from:"Hadoop QA $Commented$ $JIRA$"

[jira] [Commented] (HADOOP-8296) hadoop/yarn daemonlog usage wrong

2012-04-20 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258061#comment-13258061
]

Hadoop QA commented on HADOOP-8296:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523460/HADOOP-8296.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/872//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/872//console

This message is automatically generated.

hadoop/yarn daemonlog usage wrong
--

Key: HADOOP-8296
URL: https://issues.apache.org/jira/browse/HADOOP-8296
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.2, 2.0.0, 3.0.0
Reporter: Thomas Graves
Assignee: Devaraj K
Priority: Minor
Attachments: HADOOP-8296.patch

$ yarn daemonlog
USAGES:
java org.apache.hadoop.log.LogLevel -getlevel host:port name
java org.apache.hadoop.log.LogLevel -setlevel host:port name level
The usage shouldn't print java org.apache.hadoop.log.LogLevel

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8297) Writable javadocs don't carry default constructor

2012-04-20 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258147#comment-13258147
]

Hadoop QA commented on HADOOP-8297:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523479/HADOOP-8297.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/873//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/873//console

This message is automatically generated.

Writable javadocs don't carry default constructor
-

Key: HADOOP-8297
URL: https://issues.apache.org/jira/browse/HADOOP-8297
Project: Hadoop Common
Issue Type: Improvement
Components: io
Affects Versions: 2.0.0
Reporter: Harsh J
Assignee: Harsh J
Priority: Trivial
Attachments: HADOOP-8297.patch

The Writable API docs have a custom writable example but doesn't carry a
default constructor in it. Apparently a default constructor is required and
hence the example ought to carry it for benefit of the reader/paster.

[jira] [Commented] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader

2012-04-20 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258398#comment-13258398
]

Hadoop QA commented on HADOOP-8285:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12523523/hadoop-8285-3-common.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 5 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/874//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/874//artifact/trunk/hadoop-common-project/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/874//console

This message is automatically generated.

Use ProtoBuf for RpcPayLoadHeader
-

Key: HADOOP-8285
URL: https://issues.apache.org/jira/browse/HADOOP-8285
Project: Hadoop Common
Issue Type: Improvement
Reporter: Sanjay Radia
Assignee: Sanjay Radia
Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch,
hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch,
hadoop-8285-3.patch

[jira] [Commented] (HADOOP-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations

2012-04-19 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257846#comment-13257846
]

Hadoop QA commented on HADOOP-7549:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523408/HADOOP-7549v3.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 2 new or modified test
files.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/869//console

This message is automatically generated.

Use JDK ServiceLoader mechanism to find FileSystem implementations
--

Key: HADOOP-7549
URL: https://issues.apache.org/jira/browse/HADOOP-7549
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 0.23.0
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
Fix For: 0.24.0

Attachments: HADOOP-7549v1.patch, HADOOP-7549v2.patch,
HADOOP-7549v3.patch

Currently configuring FileSystem implementations must be done by declaring
the FileSystem class in the Hadoop configuration files (core-default.xml,
...).
Using JDK ServiceLoader mechanism this configuration step can be avoided.
Adding the JAR file with the additional FileSystem implementation would
suffice.
This is similar to what is being proposed for compression codecs
(HADOOP-7350).

[jira] [Commented] (HADOOP-8294) IPC Connection becomes unusable even if server address was temporarilly unresolvable

2012-04-19 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257903#comment-13257903
]

Hadoop QA commented on HADOOP-8294:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523425/hadoop-8294.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/870//console

This message is automatically generated.

IPC Connection becomes unusable even if server address was temporarilly
unresolvable

Key: HADOOP-8294
URL: https://issues.apache.org/jira/browse/HADOOP-8294
Project: Hadoop Common
Issue Type: Bug
Components: ipc
Affects Versions: 1.0.2
Reporter: Kihwal Lee
Assignee: Kihwal Lee
Priority: Critical
Fix For: 1.0.3, 1.1.0

Attachments: hadoop-8294.patch

This is same as HADOOP-7428, but was observed on 1.x data nodes. This can
happen more frequently after HADOOP-7472, which allows IPC Connection to
re-resolve the name. HADOOP-7428 needs to be back-ported.

[jira] [Commented] (HADOOP-8152) Expand public APIs for security library classes

2012-04-19 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257915#comment-13257915
]

Hadoop QA commented on HADOOP-8152:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523428/HADOOP-8152.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/871//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/871//console

This message is automatically generated.

Expand public APIs for security library classes
---

Key: HADOOP-8152
URL: https://issues.apache.org/jira/browse/HADOOP-8152
Project: Hadoop Common
Issue Type: Improvement
Components: security
Affects Versions: 2.0.0
Reporter: Aaron T. Myers
Assignee: Aaron T. Myers
Attachments: HADOOP-8152.patch, HADOOP-8152.patch, HADOOP-8152.patch

Currently projects like Hive and HBase use UserGroupInformation and
SecurityUtil methods. Both of these classes are marked
LimitedPrivate(HDFS,MR) but should probably be marked more generally public.

[jira] [Commented] (HADOOP-8289) Hadoop Common project build failure in cygwin

2012-04-18 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256256#comment-13256256
 ] 

Hadoop QA commented on HADOOP-8289:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12523082/common.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/863//console

This message is automatically generated.

 Hadoop Common project build failure in cygwin 
 --

 Key: HADOOP-8289
 URL: https://issues.apache.org/jira/browse/HADOOP-8289
 Project: Hadoop Common
  Issue Type: Bug
  Components: build
Affects Versions: 0.23.1
 Environment: windows, cygwin 5.2
Reporter: Biao Chen
Priority: Minor
 Attachments: common.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8253) Improper log mesage when blockreport interval comapred with initial delay

2012-04-18 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256444#comment-13256444
]

Hadoop QA commented on HADOOP-8253:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523174/Hadoop-8253.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/864//console

This message is automatically generated.

Improper log mesage when blockreport interval comapred with initial delay
-

Key: HADOOP-8253
URL: https://issues.apache.org/jira/browse/HADOOP-8253
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Brahma Reddy Battula
Priority: Minor
Attachments: Hadoop-8253.patch, Hadoop-8253.patch

Log message is telling if initialDelay is more than blockReportInterval
setting to 0.
But actuall check is greaterthan and equal..like following..It is misleading
initail I thought if it
is equal then initailBr wn't set to zero.
{code}
if (initBRDelay = blockReportInterval) {
initBRDelay = 0;
DataNode.LOG.info(dfs.blockreport.initialDelay is greater than +
dfs.blockreport.intervalMsec. + Setting initial delay to 0
msec:);
}
{code}

[jira] [Commented] (HADOOP-8290) Remove two remaining references to hadoop.native.lib oldprop

2012-04-18 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256545#comment-13256545
]

Hadoop QA commented on HADOOP-8290:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523187/HADOOP-8290.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 2 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/865//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/865//console

This message is automatically generated.

Remove two remaining references to hadoop.native.lib oldprop
--

Key: HADOOP-8290
URL: https://issues.apache.org/jira/browse/HADOOP-8290
Project: Hadoop Common
Issue Type: Improvement
Components: test
Affects Versions: 3.0.0
Reporter: Harsh J
Assignee: Harsh J
Priority: Trivial
Attachments: HADOOP-8290.patch, HADOOP-8290.patch

The following two test files still carry the old prop name:
{code}
# modified:
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/compress/TestCodec.java
# modified:
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/file/tfile/TestTFileSeqFileComparison.java
{code}
This JIRA is to merely fix those up to use the new io.native.lib.enabled prop.

[jira] [Commented] (HADOOP-8288) Remove references of mapred.child.ulimit etc. since they are not being used any more

2012-04-18 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13256624#comment-13256624
]

Hadoop QA commented on HADOOP-8288:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12523203/HADOOP-8288.branch-0.23.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/866//console

This message is automatically generated.

Remove references of mapred.child.ulimit etc. since they are not being used
any more

Key: HADOOP-8288
URL: https://issues.apache.org/jira/browse/HADOOP-8288
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.2
Reporter: Ravi Prakash
Assignee: Ravi Prakash
Attachments: HADOOP-8288.branch-0.23.patch,
HADOOP-8288.branch-0.23.patch

Courtesy Philip Su, we found that (mapred.child.ulimit, mapreduce.map.ulimit,
mapreduce.reduce.ulimit) were not being used at all. The configuration exists
but is never used. Its also mentioned in mapred-default.xml and
templates/../mapred-site.xml . Also the method getUlimitMemoryCommand in
Shell.java is now useless and can be removed.

[jira] [Commented] (HADOOP-8284) clover integration broken, also mapreduce poms are pulling in clover as a dependency

2012-04-18 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257023#comment-13257023
]

Hadoop QA commented on HADOOP-8284:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523266/HADOOP-8284.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/867//console

This message is automatically generated.

clover integration broken, also mapreduce poms are pulling in clover as a
dependency

Key: HADOOP-8284
URL: https://issues.apache.org/jira/browse/HADOOP-8284
Project: Hadoop Common
Issue Type: Bug
Components: build
Reporter: Patrick Hunt
Assignee: Patrick Hunt
Attachments: HADOOP-8284.patch, HADOOP-8284.patch

companion to MAPREDUCE-4141 - clover is broken on trunk.

[jira] [Commented] (HADOOP-8284) clover integration broken, also mapreduce poms are pulling in clover as a dependency

2012-04-18 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13257054#comment-13257054
]

Hadoop QA commented on HADOOP-8284:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12523268/HADOOP-8284.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/868//console

This message is automatically generated.

clover integration broken, also mapreduce poms are pulling in clover as a
dependency

companion to MAPREDUCE-4141 - clover is broken on trunk.

[jira] [Commented] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader

2012-04-17 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255365#comment-13255365
]

Hadoop QA commented on HADOOP-8285:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12522916/hadoop-8285-2-common.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 5 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/861//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/861//artifact/trunk/hadoop-common-project/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/861//console

This message is automatically generated.

Use ProtoBuf for RpcPayLoadHeader
-

[jira] [Commented] (HADOOP-8288) Remove references of mapred.child.ulimit etc. since they are not being used any more

2012-04-17 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255761#comment-13255761
]

Hadoop QA commented on HADOOP-8288:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12522986/HADOOP-8288.branch-0.23.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/862//console

This message is automatically generated.

Remove references of mapred.child.ulimit etc. since they are not being used
any more

[jira] [Commented] (HADOOP-8282) start-all.sh refers incorrectly start-dfs.sh existence for starting start-yarn.sh

2012-04-16 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254594#comment-13254594
]

Hadoop QA commented on HADOOP-8282:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522753/HADOOP-8282.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/853//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/853//console

This message is automatically generated.

start-all.sh refers incorrectly start-dfs.sh existence for starting
start-yarn.sh
-

Key: HADOOP-8282
URL: https://issues.apache.org/jira/browse/HADOOP-8282
Project: Hadoop Common
Issue Type: Bug
Components: scripts
Affects Versions: 2.0.0, 3.0.0
Reporter: Devaraj K
Assignee: Devaraj K
Priority: Minor
Attachments: HADOOP-8282.patch

[jira] [Commented] (HADOOP-8227) Allow RPC to limit ephemeral port range.

2012-04-16 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254764#comment-13254764
]

Hadoop QA commented on HADOOP-8227:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522785/HADOOP-8227-trunk.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/854//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/854//console

This message is automatically generated.

Allow RPC to limit ephemeral port range.

Key: HADOOP-8227
URL: https://issues.apache.org/jira/browse/HADOOP-8227
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 0.23.2
Reporter: Robert Joseph Evans
Assignee: Robert Joseph Evans
Priority: Blocker
Attachments: HADOOP-8227-trunk.txt, HADOOP-8227-trunk.txt,
HADOOP-8227-trunk.txt

This is a sub task of MAPREDUCE-4079. For security reasons we would like to
limit the range of ports that are used when some RPC servers select a port.

[jira] [Commented] (HADOOP-8283) Allow tests to control token service value

2012-04-16 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254772#comment-13254772
]

Hadoop QA commented on HADOOP-8283:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522789/HADOOP-8283.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/855//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/855//console

This message is automatically generated.

Allow tests to control token service value
--

Key: HADOOP-8283
URL: https://issues.apache.org/jira/browse/HADOOP-8283
Project: Hadoop Common
Issue Type: Test
Components: test
Affects Versions: 0.23.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-8283.patch

Tests in projects other than common need to be able to change whether the
token service uses an ip or a host.

[jira] [Commented] (HADOOP-8284) clover integration broken, also mapreduce poms are pulling in clover as a dependency

2012-04-16 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254798#comment-13254798
 ] 

Hadoop QA commented on HADOOP-8284:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12522799/HADOOP-8284.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/856//console

This message is automatically generated.

 clover integration broken, also mapreduce poms are pulling in clover as a 
 dependency
 

 Key: HADOOP-8284
 URL: https://issues.apache.org/jira/browse/HADOOP-8284
 Project: Hadoop Common
  Issue Type: Bug
  Components: build
Reporter: Patrick Hunt
Assignee: Patrick Hunt
 Attachments: HADOOP-8284.patch


 companion to MAPREDUCE-4141 - clover is broken on trunk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8172) Configuration no longer sets all keys in a deprecated key list.

2012-04-16 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254863#comment-13254863
 ] 

Hadoop QA commented on HADOOP-8172:
---

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12522820/HADOOP-8172-branch-2.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 new or modified test 
files.

+1 javadoc.  The javadoc tool did not generate any warning messages.

-1 javac.  The applied patch generated 1028 javac compiler warnings (more 
than the trunk's current 1014 warnings).

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

+1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

-1 core tests.  The patch failed these unit tests:
  org.apache.hadoop.conf.TestConfigurationDeprecation

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/857//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/857//console

This message is automatically generated.

 Configuration no longer sets all keys in a deprecated key list.
 ---

 Key: HADOOP-8172
 URL: https://issues.apache.org/jira/browse/HADOOP-8172
 Project: Hadoop Common
  Issue Type: Bug
  Components: conf
Affects Versions: 0.23.3, 0.24.0
Reporter: Robert Joseph Evans
Assignee: Anupam Seth
Priority: Blocker
 Attachments: HADOOP-8172-branch-2.patch


 I did not look at the patch for HADOOP-8167 previously, but I did in response 
 to a recent test failure. The patch appears to have changed the following 
 code (I am just paraphrasing the code)
 {code}
 if(!deprecated(key)) {
   set(key, value);
 } else {
   for(String newKey: depricatedKeyMap.get(key)) {
 set(newKey, value);
   }
 }
 {code}
 to be 
 {code}
 set(key, value);
 if(depricatedKeyMap.contains(key)) {
set(deprecatedKeyMap.get(key)[0], value);
 } else if(reverseKeyMap.contains(key)) {
set(reverseKeyMap.get(key), value);
 }
 {code}
 If a key is deprecated and is mapped to more then one new key value only the 
 first one in the list will be set, where as previously all of them would be 
 set.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8172) Configuration no longer sets all keys in a deprecated key list.

2012-04-16 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254923#comment-13254923
 ] 

Hadoop QA commented on HADOOP-8172:
---

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12522826/HADOOP-8172-branch-2.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 2 new or modified test 
files.

+1 javadoc.  The javadoc tool did not generate any warning messages.

-1 javac.  The applied patch generated 1028 javac compiler warnings (more 
than the trunk's current 1014 warnings).

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

+1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

-1 core tests.  The patch failed these unit tests:
  org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/858//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/858//console

This message is automatically generated.

 Configuration no longer sets all keys in a deprecated key list.
 ---

 Key: HADOOP-8172
 URL: https://issues.apache.org/jira/browse/HADOOP-8172
 Project: Hadoop Common
  Issue Type: Bug
  Components: conf
Affects Versions: 0.23.3, 0.24.0
Reporter: Robert Joseph Evans
Assignee: Anupam Seth
Priority: Blocker
 Attachments: HADOOP-8172-branch-2.patch, HADOOP-8172-branch-2.patch


 I did not look at the patch for HADOOP-8167 previously, but I did in response 
 to a recent test failure. The patch appears to have changed the following 
 code (I am just paraphrasing the code)
 {code}
 if(!deprecated(key)) {
   set(key, value);
 } else {
   for(String newKey: depricatedKeyMap.get(key)) {
 set(newKey, value);
   }
 }
 {code}
 to be 
 {code}
 set(key, value);
 if(depricatedKeyMap.contains(key)) {
set(deprecatedKeyMap.get(key)[0], value);
 } else if(reverseKeyMap.contains(key)) {
set(reverseKeyMap.get(key), value);
 }
 {code}
 If a key is deprecated and is mapped to more then one new key value only the 
 first one in the list will be set, where as previously all of them would be 
 set.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader

2012-04-16 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255046#comment-13255046
]

Hadoop QA commented on HADOOP-8285:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12522846/hadoop-8285-1-common.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 5 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

-1 javac. The patch appears to cause tar ant target to fail.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/859//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/859//console

This message is automatically generated.

Use ProtoBuf for RpcPayLoadHeader
-

[jira] [Commented] (HADOOP-8286) Simplify getting a socket address from conf

2012-04-16 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255113#comment-13255113
]

Hadoop QA commented on HADOOP-8286:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522868/HADOOP-8286.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/860//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/860//console

This message is automatically generated.

Simplify getting a socket address from conf
---

Key: HADOOP-8286
URL: https://issues.apache.org/jira/browse/HADOOP-8286
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Affects Versions: 0.23.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-8286.patch

{{NetUtils.createSocketAddr(addr, port, confKey}} will throw an exception
with a descriptive message of a malformed conf value. A corresponding
{{conf#getSocketAddr}} would make it easier to use, and ensure that
{{NetUtils}} is used to parse the address.

[jira] [Commented] (HADOOP-7350) Use ServiceLoader to discover compression codec classes

2012-04-13 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13253653#comment-13253653
]

Hadoop QA commented on HADOOP-7350:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522601/HADOOP-7350.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/850//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/850//console

This message is automatically generated.

Use ServiceLoader to discover compression codec classes
---

Key: HADOOP-7350
URL: https://issues.apache.org/jira/browse/HADOOP-7350
Project: Hadoop Common
Issue Type: Improvement
Components: conf, io
Reporter: Tom White
Assignee: Tom White
Attachments: HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch,
HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch, HADOOP-7350.patch,
HADOOP-7350.patch

By using a ServiceLoader users wouldn't have to add codec classes to
io.compression.codecs for codecs that aren't shipped with Hadoop (e.g. LZO),
since they would be automatically picked up from the classpath.

[jira] [Commented] (HADOOP-8275) harden serialization logic against malformed or malicious input

2012-04-13 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13253847#comment-13253847
]

Hadoop QA commented on HADOOP-8275:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522627/HADOOP-8275.001.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/851//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/851//console

This message is automatically generated.

harden serialization logic against malformed or malicious input
---

Key: HADOOP-8275
URL: https://issues.apache.org/jira/browse/HADOOP-8275
Project: Hadoop Common
Issue Type: Bug
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
Attachments: HADOOP-8275.001.patch

harden serialization logic against malformed or malicious input

[jira] [Commented] (HADOOP-8275) harden serialization logic against malformed or malicious input

2012-04-13 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13253911#comment-13253911
]

Hadoop QA commented on HADOOP-8275:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522643/HADOOP-8275.002.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/852//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/852//console

This message is automatically generated.

harden serialization logic against malformed or malicious input
---

Key: HADOOP-8275
URL: https://issues.apache.org/jira/browse/HADOOP-8275
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
Fix For: 2.0.0

Attachments: HADOOP-8275.001.patch, HADOOP-8275.002.patch

harden serialization logic against malformed or malicious input

[jira] [Commented] (HADOOP-8232) Provide a command line entry point to view/test topology options

2012-04-12 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252638#comment-13252638
]

Hadoop QA commented on HADOOP-8232:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522448/HADOOP-8232.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/849//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/849//console

This message is automatically generated.

Provide a command line entry point to view/test topology options

Key: HADOOP-8232
URL: https://issues.apache.org/jira/browse/HADOOP-8232
Project: Hadoop Common
Issue Type: Sub-task
Components: util
Affects Versions: 0.23.1
Reporter: Steve Loughran
Assignee: Steve Loughran
Priority: Minor
Attachments: HADOOP-8232.patch, HADOOP-8232.patch

Add a new command line entry point topo with commands for preflight
checking of a clusters topology setup.
The initial operations would be to list the implementation class of the
mapper, and attempt to load it, resolve a set of supplied hostnames, then
dump the topology map after the resolution process.
Target audience:
# ops teams trying to get a new/changed script working before deploying it on
a cluster.
# someone trying to write their first script.
Resolve and list the rack mappings of the given host
{code}
hadoop topo test [host1] [host2] ...
{code}
This would load the hostnames from a given file, resolve all of them and list
the results:
{code}
hadoop topo testfile filename
{code}
This version is intended for the ops team who have a list of hostnames, IP
addresses.
* Rather than just list them, the ops team may want to mandate that there
were no /default-rack mappings found, as that is invariably a sign that the
script isn't handling a hostname properly.
* No attempt to be clever and do IP address resolution, FQDN to hostname
mapping, etc.

[jira] [Commented] (HADOOP-8268) hadoop-project-dist/pom.xml fails XML validation

2012-04-11 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251477#comment-13251477
]

Hadoop QA commented on HADOOP-8268:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/1253/hadoop-pom.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/844//console

This message is automatically generated.

hadoop-project-dist/pom.xml fails XML validation

Key: HADOOP-8268
URL: https://issues.apache.org/jira/browse/HADOOP-8268
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 0.23.0
Environment: FreeBSD 8.2 / AMD64
Reporter: Radim Kolar
Labels: maven, patch
Attachments: hadoop-pom.txt

In this pom file are embedded ant commands which contains '' - redirection.
This makes XML file invalid and this POM file can not be deployed into
validating Maven repository managers such as Artifactory.

[jira] [Commented] (HADOOP-7510) Tokens should use original hostname provided instead of ip

2012-04-11 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251697#comment-13251697
]

Hadoop QA commented on HADOOP-7510:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12522265/HADOOP-7510.branch-0.23.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/845//console

This message is automatically generated.

Tokens should use original hostname provided instead of ip
--

Key: HADOOP-7510
URL: https://issues.apache.org/jira/browse/HADOOP-7510
Project: Hadoop Common
Issue Type: Improvement
Components: security
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Fix For: 0.20.205.0, 0.24.0

Attachments: HADOOP-7510-10.patch, HADOOP-7510-11.patch,
HADOOP-7510-12.patch, HADOOP-7510-2.patch, HADOOP-7510-3.patch,
HADOOP-7510-4.patch, HADOOP-7510-5.patch, HADOOP-7510-6.patch,
HADOOP-7510-8.patch, HADOOP-7510-9.patch, HADOOP-7510.branch-0.23.patch,
HADOOP-7510.patch, HADOOP-7510.trunk.patch

Tokens currently store the ip:port of the remote server. This precludes
tokens from being used after a host's ip is changed. Tokens should store the
hostname used to make the RPC connection. This will enable new processes to
use their existing tokens.

[jira] [Commented] (HADOOP-8144) pseudoSortByDistance in NetworkTopology doesn't work properly if no local node and first node is local rack node

2012-04-11 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252040#comment-13252040
]

Hadoop QA commented on HADOOP-8144:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522341/hadoop-8144.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/846//console

This message is automatically generated.

pseudoSortByDistance in NetworkTopology doesn't work properly if no local
node and first node is local rack node

Key: HADOOP-8144
URL: https://issues.apache.org/jira/browse/HADOOP-8144
Project: Hadoop Common
Issue Type: Bug
Components: io
Affects Versions: 1.0.0, 0.23.0
Reporter: Junping Du
Assignee: Junping Du
Priority: Minor
Labels: patch
Attachments: HADOOP-8144-1.patch, HADOOP-8144-v2.patch,
hadoop-8144.txt

pseudoSortByDistance in NetworkTopology.java should sort nodes according to
its distance with reader as local node, local rack node, ...
But if there is no local node with reader in nodes and the first node is
local rack node with reader, then it will put a random node at position 0.

[jira] [Commented] (HADOOP-8270) hadoop-daemon.sh stop action is not LSB compliant

2012-04-11 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252051#comment-13252051
]

Hadoop QA commented on HADOOP-8270:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522342/HADOOP-8270.patch.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/847//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/847//console

This message is automatically generated.

hadoop-daemon.sh stop action is not LSB compliant
-

Key: HADOOP-8270
URL: https://issues.apache.org/jira/browse/HADOOP-8270
Project: Hadoop Common
Issue Type: Bug
Components: scripts
Affects Versions: 0.23.1
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik
Fix For: 2.0.0

Attachments: HADOOP-8270.patch.txt

The following bit of code from hadoop-daemon.sh is not LSB compliant, since
according to
http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
a stop action on an already stopped service should return 0.
{noformat}
(stop)
if [ -f $pid ]; then
if kill -0 `cat $pid` /dev/null 21; then
echo stopping $command
kill `cat $pid`
else
echo no $command to stop
exit 1
fi
else
echo no $command to stop
exit 1
fi
;;
{noformat}

[jira] [Commented] (HADOOP-8144) pseudoSortByDistance in NetworkTopology doesn't work properly if no local node and first node is local rack node

2012-04-11 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252074#comment-13252074
]

Hadoop QA commented on HADOOP-8144:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522348/hadoop-8144.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/848//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/848//console

This message is automatically generated.

pseudoSortByDistance in NetworkTopology doesn't work properly if no local
node and first node is local rack node

[jira] [Commented] (HADOOP-8264) Remove irritating double double quotes in front of hostname

2012-04-10 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250602#comment-13250602
]

Hadoop QA commented on HADOOP-8264:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12522091/hadoop-8264-quoting.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/843//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/843//console

This message is automatically generated.

Remove irritating double double quotes in front of hostname

Key: HADOOP-8264
URL: https://issues.apache.org/jira/browse/HADOOP-8264
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.2
Reporter: Bernd Fondermann
Assignee: Bernd Fondermann
Priority: Trivial
Attachments: hadoop-8264-quoting.patch

The attached patch fixes display of destination port from hostname to
hostname

[jira] [Commented] (HADOOP-8261) Har file system doesn't deal with FS URIs with a host but no port

2012-04-09 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13249692#comment-13249692
]

Hadoop QA commented on HADOOP-8261:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521910/HADOOP-8261.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/839//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/839//console

This message is automatically generated.

Har file system doesn't deal with FS URIs with a host but no port
-

Key: HADOOP-8261
URL: https://issues.apache.org/jira/browse/HADOOP-8261
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.0
Reporter: Aaron T. Myers
Assignee: Aaron T. Myers
Fix For: 2.0.0

Attachments: HADOOP-8261-with-test-in-HDFS.patch, HADOOP-8261.patch,
HADOOP-8261.patch

If you try to run an MR job with a Hadoop Archive as the input, but the URI
you give it has no port specified (e.g. hdfs://simon) the job will fail
with an error like the following:
{noformat}
java.io.IOException: Incomplete HDFS URI, no host:
hdfs://simon:-1/user/atm/input.har/input
{noformat}

[jira] [Commented] (HADOOP-8152) Expand public APIs for security library classes

2012-04-09 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13249720#comment-13249720
]

Hadoop QA commented on HADOOP-8152:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521917/HADOOP-8152.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/840//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/840//console

This message is automatically generated.

Expand public APIs for security library classes
---

Currently projects like Hive and HBase use UserGroupInformation and
SecurityUtil methods. Both of these classes are marked
LimitedPrivate(HDFS,MR) but should probably be marked more generally public.

[jira] [Commented] (HADOOP-8227) Allow RPC to limit ephemeral port range.

2012-04-09 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13249878#comment-13249878
]

Hadoop QA commented on HADOOP-8227:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521962/HADOOP-8227-trunk.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 2 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/841//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/841//console

This message is automatically generated.

Allow RPC to limit ephemeral port range.

This is a sub task of MAPREDUCE-4079. For security reasons we would like to
limit the range of ports that are used when some RPC servers select a port.

[jira] [Commented] (HADOOP-8263) Stringification of IPC calls not useful

2012-04-09 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13250339#comment-13250339
]

Hadoop QA commented on HADOOP-8263:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522041/hadoop-8263.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/842//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/842//console

This message is automatically generated.

Stringification of IPC calls not useful
---

Key: HADOOP-8263
URL: https://issues.apache.org/jira/browse/HADOOP-8263
Project: Hadoop Common
Issue Type: Bug
Components: ipc
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Minor
Attachments: hadoop-8263.txt

Since the Protobufification of Hadoop, the log messages on IPC exceptions on
the server side now read like:
12/04/09 16:04:06 INFO ipc.Server: IPC Server handler 9 on 8021, call
org.apache.hadoop.ipc.ProtobufRpcEngine$RpcRequestWritable@7087e9bf from
127.0.0.1:47989: error: org.apache.hadoop.ipc.StandbyException: Operation
category READ is not supported in state standby
The call should instead stringify the method name and the request protobuf
(perhaps abbreviated if it is longer than a few hundred chars)

[jira] [Commented] (HADOOP-8253) Improper log mesage when blockreport interval comapred with initial delay

2012-04-07 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13249234#comment-13249234
]

Hadoop QA commented on HADOOP-8253:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521816/Hadoop-8253.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/837//console

This message is automatically generated.

Improper log mesage when blockreport interval comapred with initial delay
-

Key: HADOOP-8253
URL: https://issues.apache.org/jira/browse/HADOOP-8253
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Brahma Reddy Battula
Priority: Minor
Attachments: Hadoop-8253.patch

[jira] [Commented] (HADOOP-8152) Expand public APIs for security library classes

2012-04-07 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13249301#comment-13249301
]

Hadoop QA commented on HADOOP-8152:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521709/HADOOP-8152.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/838//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/838//console

This message is automatically generated.

Expand public APIs for security library classes
---

Currently projects like Hive and HBase use UserGroupInformation and
SecurityUtil methods. Both of these classes are marked
LimitedPrivate(HDFS,MR) but should probably be marked more generally public.

[jira] [Commented] (HADOOP-8075) Lower native-hadoop library log from info to debug

2012-04-06 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13248336#comment-13248336
]

Hadoop QA commented on HADOOP-8075:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520276/HDFS-8075.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/830//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/830//console

This message is automatically generated.

Lower native-hadoop library log from info to debug
---

Key: HADOOP-8075
URL: https://issues.apache.org/jira/browse/HADOOP-8075
Project: Hadoop Common
Issue Type: Improvement
Components: native
Affects Versions: 0.23.0
Reporter: Eli Collins
Labels: newbie
Attachments: HDFS-8075.patch

The following log shows up in all commands. It's useful to have it in the
server log, but let's figure out a way so that it isn't logged eg every time
you cat a file.
{noformat}
[eli@centos6 ~]$ hadoop fs -cat /user/eli/foo
12/02/12 20:10:20 INFO util.NativeCodeLoader: Loaded the native-hadoop library
{noformat}

[jira] [Commented] (HADOOP-8014) ViewFileSystem does not correctly implement getDefaultBlockSize, getDefaultReplication, getContentSummary

2012-04-06 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13248466#comment-13248466
]

Hadoop QA commented on HADOOP-8014:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521558/HADOOP-8014.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 2 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/831//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/831//console

This message is automatically generated.

ViewFileSystem does not correctly implement getDefaultBlockSize,
getDefaultReplication, getContentSummary
-

Key: HADOOP-8014
URL: https://issues.apache.org/jira/browse/HADOOP-8014
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 0.23.0, 0.23.2, 0.24.0
Reporter: Daryn Sharp
Assignee: John George
Attachments: HADOOP-8014.patch, HADOOP-8014.patch, HADOOP-8014.patch,
HADOOP-8014.patch, HADOOP-8014.patch, HADOOP-8014.patch

{{ViewFileSystem}} incorrectly returns the {{FileSystem}} default values for
{{getDefaultBlockSize()}} and {{getDefaultReplication()}}. This causes files
to be created with incorrect values. The problem is that the current apis
are insufficient for viewfs because the defaults depend on the underlying
mount point. These methods need counterparts that accept a {{Path}} so
viewfs can resolve the mount point for a path.

[jira] [Commented] (HADOOP-8014) ViewFileSystem does not correctly implement getDefaultBlockSize, getDefaultReplication, getContentSummary

2012-04-06 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13248497#comment-13248497
]

Hadoop QA commented on HADOOP-8014:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521694/HADOOP-8014.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 2 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/832//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/832//console

This message is automatically generated.

ViewFileSystem does not correctly implement getDefaultBlockSize,
getDefaultReplication, getContentSummary
-

[jira] [Commented] (HADOOP-7510) Tokens should use original hostname provided instead of ip

2012-04-06 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13248515#comment-13248515
]

Hadoop QA commented on HADOOP-7510:
---

+1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12521695/HADOOP-7510.trunk.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/833//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/833//console

This message is automatically generated.

Tokens should use original hostname provided instead of ip
--

[jira] [Commented] (HADOOP-8249) invalid hadoop-auth cookies should trigger authentication if info is avail before returning HTTP 401

2012-04-05 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247117#comment-13247117
 ] 

Hadoop QA commented on HADOOP-8249:
---

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12521475/HADOOP-8249.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 3 new or modified tests.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

+1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

+1 core tests.  The patch passed unit tests in .

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/822//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/822//console

This message is automatically generated.

 invalid hadoop-auth cookies should trigger authentication if info is avail 
 before returning HTTP 401
 

 Key: HADOOP-8249
 URL: https://issues.apache.org/jira/browse/HADOOP-8249
 Project: Hadoop Common
  Issue Type: Bug
  Components: security
Affects Versions: 0.23.1, 2.0.0
Reporter: bc Wong
Assignee: Alejandro Abdelnur
 Fix For: 2.0.0

 Attachments: HADOOP-8249.patch


 WebHdfs gives out cookies. But when the client passes them back, it'd 
 sometimes reject them and return a HTTP 401 instead. (Sometimes as in after 
 a restart.) The interesting thing is that if the client doesn't pass the 
 cookie back, WebHdfs will be totally happy.
 The correct behaviour should be to ignore the cookie if it looks invalid, and 
 attempt to proceed with the request handling.
 I haven't tried HttpFs to see whether it handles restart better.
 Reproducing it with curl:
 {noformat}
 
 ## Initial curl. Storing cookie to file.
 
 [root@vbox2 ~]# curl -c /tmp/webhdfs.cookie -i 
 'http://localhost:50070/webhdfs/v1/?op=LISTSTATUSuser.name=bcwalrus'
 HTTP/1.1 200 OK
 Content-Type: application/json
 Expires: Thu, 01-Jan-1970 00:00:00 GMT
 Set-Cookie: 
 hadoop.auth=u=bcwalrusp=bcwalrust=simplee=1333614686366s=z2w5xpFlufnnEoOHxVRiXqxwtqM=;Path=/
 Content-Length: 597
 Server: Jetty(6.1.26)
 {FileStatuses:{FileStatus:[
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577906198,owner:mapred,pathSuffix:tmp,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577511848,owner:hdfs,pathSuffix:user,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333428745116,owner:mapred,pathSuffix:var,permission:755,replication:0,type:DIRECTORY}
 ]}}
 
 ## Another curl. Using the cookie jar.
 
 [root@vbox2 ~]# curl -b /tmp/webhdfs.cookie -i 
 'http://localhost:50070/webhdfs/v1/?op=LISTSTATUSuser.name=bcwalrus'
 HTTP/1.1 200 OK
 Content-Type: application/json
 Content-Length: 597
 Server: Jetty(6.1.26)
 {FileStatuses:{FileStatus:[
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577906198,owner:mapred,pathSuffix:tmp,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577511848,owner:hdfs,pathSuffix:user,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333428745116,owner:mapred,pathSuffix:var,permission:755,replication:0,type:DIRECTORY}
 ]}}
 
 ## Restart NN.
 
 [root@vbox2 ~]# /etc/init.d/hadoop-hdfs-namenode restartStopping Hadoop 
 namenode:  [  OK  ]
 stopping namenode
 Starting Hadoop namenode:  [  OK  ]
 starting namenode, logging to 
 /var/log/hadoop-hdfs/hadoop-hdfs-namenode-vbox2.out
 
 ## Curl using cookie jar gives error.
 
 [root@vbox2 ~]# curl -b /tmp/webhdfs.cookie -i

[jira] [Commented] (HADOOP-8249) invalid hadoop-auth cookies should trigger authentication if info is avail before returning HTTP 401

2012-04-05 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247217#comment-13247217
 ] 

Hadoop QA commented on HADOOP-8249:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12521475/HADOOP-8249.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 3 new or modified tests.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

+1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

-1 core tests.  The patch failed these unit tests:
  org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/824//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/824//console

This message is automatically generated.

 invalid hadoop-auth cookies should trigger authentication if info is avail 
 before returning HTTP 401
 

 Key: HADOOP-8249
 URL: https://issues.apache.org/jira/browse/HADOOP-8249
 Project: Hadoop Common
  Issue Type: Bug
  Components: security
Affects Versions: 0.23.1, 2.0.0
Reporter: bc Wong
Assignee: Alejandro Abdelnur
 Fix For: 2.0.0

 Attachments: HADOOP-8249.patch


 WebHdfs gives out cookies. But when the client passes them back, it'd 
 sometimes reject them and return a HTTP 401 instead. (Sometimes as in after 
 a restart.) The interesting thing is that if the client doesn't pass the 
 cookie back, WebHdfs will be totally happy.
 The correct behaviour should be to ignore the cookie if it looks invalid, and 
 attempt to proceed with the request handling.
 I haven't tried HttpFs to see whether it handles restart better.
 Reproducing it with curl:
 {noformat}
 
 ## Initial curl. Storing cookie to file.
 
 [root@vbox2 ~]# curl -c /tmp/webhdfs.cookie -i 
 'http://localhost:50070/webhdfs/v1/?op=LISTSTATUSuser.name=bcwalrus'
 HTTP/1.1 200 OK
 Content-Type: application/json
 Expires: Thu, 01-Jan-1970 00:00:00 GMT
 Set-Cookie: 
 hadoop.auth=u=bcwalrusp=bcwalrust=simplee=1333614686366s=z2w5xpFlufnnEoOHxVRiXqxwtqM=;Path=/
 Content-Length: 597
 Server: Jetty(6.1.26)
 {FileStatuses:{FileStatus:[
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577906198,owner:mapred,pathSuffix:tmp,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577511848,owner:hdfs,pathSuffix:user,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333428745116,owner:mapred,pathSuffix:var,permission:755,replication:0,type:DIRECTORY}
 ]}}
 
 ## Another curl. Using the cookie jar.
 
 [root@vbox2 ~]# curl -b /tmp/webhdfs.cookie -i 
 'http://localhost:50070/webhdfs/v1/?op=LISTSTATUSuser.name=bcwalrus'
 HTTP/1.1 200 OK
 Content-Type: application/json
 Content-Length: 597
 Server: Jetty(6.1.26)
 {FileStatuses:{FileStatus:[
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577906198,owner:mapred,pathSuffix:tmp,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333577511848,owner:hdfs,pathSuffix:user,permission:1777,replication:0,type:DIRECTORY},
 {accessTime:0,blockSize:0,group:supergroup,length:0,modificationTime:1333428745116,owner:mapred,pathSuffix:var,permission:755,replication:0,type:DIRECTORY}
 ]}}
 
 ## Restart NN.
 
 [root@vbox2 ~]# /etc/init.d/hadoop-hdfs-namenode restartStopping Hadoop 
 namenode:  [  OK  ]
 stopping namenode
 Starting Hadoop namenode:  [  OK  ]
 starting namenode, logging to 
 /var/log/hadoop-hdfs/hadoop-hdfs-namenode-vbox2.out
 
 ## Curl using cookie jar gives error.
 
 [root@vbox2 ~]# curl -b /tmp/webhdfs.cookie -i

[jira] [Commented] (HADOOP-8086) KerberosName silently sets defaultRealm to if the Kerberos config is not found, it should log a WARN

2012-04-05 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247218#comment-13247218
]

Hadoop QA commented on HADOOP-8086:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521479/HADOOP-8086.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/823//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/823//console

This message is automatically generated.

KerberosName silently sets defaultRealm to if the Kerberos config is not
found, it should log a WARN
---

Key: HADOOP-8086
URL: https://issues.apache.org/jira/browse/HADOOP-8086
Project: Hadoop Common
Issue Type: Improvement
Components: security
Affects Versions: 0.23.2, 0.24.0
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
Priority: Minor
Fix For: 0.23.2

Attachments: HADOOP-8086.patch

[jira] [Commented] (HADOOP-6963) Fix FileUtil.getDU. It should not include the size of the directory or follow symbolic links

2012-04-05 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247308#comment-13247308
]

Hadoop QA commented on HADOOP-6963:
---

+1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12521513/HADOOP-6963.branch-23.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/826//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/826//console

This message is automatically generated.

Fix FileUtil.getDU. It should not include the size of the directory or follow
symbolic links

Key: HADOOP-6963
URL: https://issues.apache.org/jira/browse/HADOOP-6963
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 0.20.205.0, 0.23.1
Reporter: Owen O'Malley
Assignee: Ravi Prakash
Priority: Critical
Attachments: HADOOP-6963.branch-1.0.2.patch,
HADOOP-6963.branch-1.0.2.patch, HADOOP-6963.branch-23.patch,
HADOOP-6963.branch-23.patch, HADOOP-6963.branch-23.patch

The getDU method should not include the size of the directory. The Java
interface says that the value is undefined and in Linux/Sun it gets the 4096
for the inode. Clearly this isn't useful.
It also recursively calls itself. In case the directory has a symbolic link
forming a cycle, getDU keeps spinning in the cycle. In our case, we saw this
in the org.apache.hadoop.mapred.JobLocalizer.downloadPrivateCacheObjects
call. This prevented other tasks on the same node from committing, causing
the TT to become effectively useless (because the JT thinks it already has
enough tasks running)

[jira] [Commented] (HADOOP-6963) Fix FileUtil.getDU. It should not include the size of the directory or follow symbolic links

2012-04-05 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247314#comment-13247314
]

Hadoop QA commented on HADOOP-6963:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12521518/HADOOP-6963.branch-1.0.2.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 1 new or modified test
files.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/827//console

This message is automatically generated.

Fix FileUtil.getDU. It should not include the size of the directory or follow
symbolic links

[jira] [Commented] (HADOOP-8180) Remove hsqldb since its not needed from pom.xml

2012-04-05 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247430#comment-13247430
 ] 

Hadoop QA commented on HADOOP-8180:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12518695/HADOOP-8180.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/828//console

This message is automatically generated.

 Remove hsqldb since its not needed from pom.xml
 ---

 Key: HADOOP-8180
 URL: https://issues.apache.org/jira/browse/HADOOP-8180
 Project: Hadoop Common
  Issue Type: Bug
Affects Versions: 0.23.2
Reporter: Ravi Prakash
Assignee: Ravi Prakash
 Attachments: HADOOP-8180.patch


 Related to MAPREDUCE-3621

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8251) SecurityUtil.fetchServiceTicket broken after HADOOP-6941

2012-04-05 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13248042#comment-13248042
]

Hadoop QA commented on HADOOP-8251:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521640/hadoop-8251.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/829//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/829//console

This message is automatically generated.

SecurityUtil.fetchServiceTicket broken after HADOOP-6941

Key: HADOOP-8251
URL: https://issues.apache.org/jira/browse/HADOOP-8251
Project: Hadoop Common
Issue Type: Bug
Components: security
Affects Versions: 1.1.0, 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Blocker
Attachments: hadoop-8251.txt

HADOOP-6941 replaced direct references to some classes with reflective access
so as to support other JDKs. Unfortunately there was a mistake in the name of
the Krb5Util class, which broke fetchServiceTicket. This manifests itself as
the inability to run checkpoints or other krb5-SSL HTTP-based transfers:
java.lang.ClassNotFoundException: sun.security.jgss.krb5

[jira] [Commented] (HADOOP-8007) HA: use substitution token for fencing argument

2012-04-04 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246098#comment-13246098
]

Hadoop QA commented on HADOOP-8007:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521287/hadoop-8007.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash
org.apache.hadoop.ha.TestZKFailoverController

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/818//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/818//console

This message is automatically generated.

HA: use substitution token for fencing argument
---

Key: HADOOP-8007
URL: https://issues.apache.org/jira/browse/HADOOP-8007
Project: Hadoop Common
Issue Type: Improvement
Components: ha
Affects Versions: 2.0.0
Reporter: Aaron T. Myers
Assignee: Todd Lipcon
Attachments: hadoop-8007.txt, hadoop-8007.txt

Per HADOOP-7983 currently the fencer always passes the target host:port to
fence as the first argument to the fence script, it would be better to use a
substitution token. That is to say, the user would configure myfence.sh
$TARGETHOST foo bar and Hadoop would substitute the target. This would allow
use of pre-existing scripts that might have a different ordering of arguments
without a wrapper.

[jira] [Commented] (HADOOP-6963) Fix FileUtil.getDU. It should not include the size of the directory or follow symbolic links

2012-04-04 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-6963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246652#comment-13246652
]

Hadoop QA commented on HADOOP-6963:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12521370/HADOOP-6963.branch-23.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/819//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/819//artifact/trunk/hadoop-common-project/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/819//console

This message is automatically generated.

Fix FileUtil.getDU. It should not include the size of the directory or follow
symbolic links

[jira] [Commented] (HADOOP-8234) Enable user group mappings on Windows

2012-04-04 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246838#comment-13246838
 ] 

Hadoop QA commented on HADOOP-8234:
---

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12521414/HADOOP-8234.branch-1-win.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 15 new or modified tests.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/820//console

This message is automatically generated.

 Enable user group mappings on Windows
 -

 Key: HADOOP-8234
 URL: https://issues.apache.org/jira/browse/HADOOP-8234
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: native
Affects Versions: 1.0.0
Reporter: Bikas Saha
Assignee: Bikas Saha
 Attachments: HADOOP-8234.branch-1-win.patch


 The initial patch submitted is missing mapping of users to groups. A number 
 of test failures are related to this. The jira tracks adding this support.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8244) Improve comments on ByteBufferReadable.read

2012-04-04 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13246863#comment-13246863
]

Hadoop QA commented on HADOOP-8244:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521416/HADOOP-8244.1.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/821//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/821//console

This message is automatically generated.

Improve comments on ByteBufferReadable.read
---

Key: HADOOP-8244
URL: https://issues.apache.org/jira/browse/HADOOP-8244
Project: Hadoop Common
Issue Type: Improvement
Reporter: Henry Robinson
Assignee: Henry Robinson
Fix For: 0.24.0

Attachments: HADOOP-8244.0.patch, HADOOP-8244.1.patch

There are a couple of ways in which the comment on ByteBufferReadable.read
can be improved. Since this is a public-facing API with potentially many
implementations, it's worth taking the time to get it right.
* We should describe what can become of the byte buffer state in the case of
an exception (is the limit changed? where's the position?). For the
DFSInputStream implementation, position and limit are unchanged if there is
an error, but I don't think that's the right think to mandate for all
implementations.
* We should mention explicitly that 0-byte reads are legitimate - this is
particularly important in light of HDFS-3110 which detects support for direct
reads by issuing a 0-byte read from libhdfs.

[jira] [Commented] (HADOOP-8244) Improve comments on ByteBufferReadable.read

2012-04-03 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13245744#comment-13245744
]

Hadoop QA commented on HADOOP-8244:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521203/HADOOP-8244.0.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/816//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/816//console

This message is automatically generated.

Improve comments on ByteBufferReadable.read
---

Key: HADOOP-8244
URL: https://issues.apache.org/jira/browse/HADOOP-8244
Project: Hadoop Common
Issue Type: Improvement
Reporter: Henry Robinson
Assignee: Henry Robinson
Attachments: HADOOP-8244.0.patch

[jira] [Commented] (HADOOP-8241) Building package fails under Windows

2012-04-02 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13244423#comment-13244423
 ] 

Hadoop QA commented on HADOOP-8241:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12521000/FixPackageBuild.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/812//console

This message is automatically generated.

 Building package fails under Windows
 

 Key: HADOOP-8241
 URL: https://issues.apache.org/jira/browse/HADOOP-8241
 Project: Hadoop Common
  Issue Type: Bug
  Components: build
Affects Versions: 0.23.1
 Environment: Windows
Reporter: Mostafa Elhemali
 Fix For: 0.23.2

 Attachments: FixPackageBuild.patch


 After applying the patch in 
 [MAPREDUCE-3540|https://issues.apache.org/jira/browse/MAPREDUCE-3540] the 
 build fails if you do mvn clean package under Windows, in 
 hadoop-hdfs-project and hadoop-dist.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8242) AbstractDelegationTokenIdentifier: add getter methods for owner and realuser

2012-04-02 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13244477#comment-13244477
]

Hadoop QA commented on HADOOP-8242:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521007/HADOOP-8242.001.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/813//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/813//console

This message is automatically generated.

AbstractDelegationTokenIdentifier: add getter methods for owner and realuser

Key: HADOOP-8242
URL: https://issues.apache.org/jira/browse/HADOOP-8242
Project: Hadoop Common
Issue Type: Improvement
Reporter: Colin Patrick McCabe
Assignee: Colin Patrick McCabe
Priority: Minor
Attachments: HADOOP-8242.001.patch

AbstractDelegationTokenIdentifier: add getter methods for owner and realuser.
This is needed for another change in HDFS.

[jira] [Commented] (HADOOP-8243) Security support broken in CLI (manual) failover controller

2012-04-02 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13244675#comment-13244675
]

Hadoop QA commented on HADOOP-8243:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12521040/hadoop-8243.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/814//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/814//console

This message is automatically generated.

Security support broken in CLI (manual) failover controller
---

Key: HADOOP-8243
URL: https://issues.apache.org/jira/browse/HADOOP-8243
Project: Hadoop Common
Issue Type: Bug
Components: ha, security
Affects Versions: 2.0.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
Attachments: hadoop-8243.txt

Some recent refactoring accidentally caused the proxies in some places to get
created with a default Configuration, instead of using the Configuration set
up by the DFSHAAdmin tool. This causes the HAServiceProtocol to be missing
the configuration which specifies the NN principle -- and thus breaks the CLI
HAAdmin tool in secure setups.

[jira] [Commented] (HADOOP-8241) Building package fails under Windows

2012-04-02 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13244865#comment-13244865
 ] 

Hadoop QA commented on HADOOP-8241:
---

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12521081/FixPackageBuild-CommonPart.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/815//console

This message is automatically generated.

 Building package fails under Windows
 

 Key: HADOOP-8241
 URL: https://issues.apache.org/jira/browse/HADOOP-8241
 Project: Hadoop Common
  Issue Type: Bug
  Components: build
Affects Versions: 0.23.1
 Environment: Windows
Reporter: Mostafa Elhemali
 Fix For: 0.23.2

 Attachments: FixPackageBuild-CommonPart.patch, FixPackageBuild.patch


 After applying the patch in 
 [MAPREDUCE-3540|https://issues.apache.org/jira/browse/MAPREDUCE-3540] the 
 build fails if you do mvn clean package under Windows, in 
 hadoop-hdfs-project and hadoop-dist.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8238) NetUtils#getHostNameOfIP blows up if given ip:port string w/o port

2012-04-01 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13243827#comment-13243827
]

Hadoop QA commented on HADOOP-8238:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520843/hadoop-8238.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/808//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/808//console

This message is automatically generated.

NetUtils#getHostNameOfIP blows up if given ip:port string w/o port
--

Key: HADOOP-8238
URL: https://issues.apache.org/jira/browse/HADOOP-8238
Project: Hadoop Common
Issue Type: Bug
Reporter: Eli Collins
Assignee: Eli Collins
Attachments: hadoop-8238.txt

NetUtils#getHostNameOfIP blows up if not given a string of form ip:port,
because the regex matches the port optionally but the code requires a
semicolon. It also doesn't check the given string for null.

[jira] [Commented] (HADOOP-8210) Common side of HDFS-3148

2012-04-01 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13243888#comment-13243888
]

Hadoop QA commented on HADOOP-8210:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520846/hadoop-8210.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/809//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/809//console

This message is automatically generated.

Common side of HDFS-3148

Key: HADOOP-8210
URL: https://issues.apache.org/jira/browse/HADOOP-8210
Project: Hadoop Common
Issue Type: Sub-task
Components: io, performance
Reporter: Eli Collins
Assignee: Eli Collins
Attachments: hadoop-8210.txt, hadoop-8210.txt

Common side of HDFS-3148, add necessary DNS and NetUtils methods. Test
coverage is in the HDFS-3148 patch.

[jira] [Commented] (HADOOP-8236) haadmin should have configurable timeouts for failover commands

2012-04-01 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13243955#comment-13243955
]

Hadoop QA commented on HADOOP-8236:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520865/hadoop-8236.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/810//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/810//console

This message is automatically generated.

haadmin should have configurable timeouts for failover commands
---

Key: HADOOP-8236
URL: https://issues.apache.org/jira/browse/HADOOP-8236
Project: Hadoop Common
Issue Type: Improvement
Components: ha
Affects Versions: 0.23.3
Reporter: Philip Zeyliger
Assignee: Todd Lipcon
Attachments: hadoop-8236.txt, hadoop-8236.txt

The HAAdmin failover could should time out reasonably aggressively and go
onto the fencing strategies if it's dealing with a mostly dead active
namenode. Currently it uses what's probably the default, which is to say no
timeout whatsoever.
{code}
/**
* Return a proxy to the specified target service.
*/
protected HAServiceProtocol getProtocol(String serviceId)
throws IOException {
String serviceAddr = getServiceAddr(serviceId);
InetSocketAddress addr = NetUtils.createSocketAddr(serviceAddr);
return (HAServiceProtocol)RPC.getProxy(
HAServiceProtocol.class, HAServiceProtocol.versionID,
addr, getConf());
}
{code}

[jira] [Commented] (HADOOP-8227) Allow RPC to limit ephemeral port range.

2012-03-30 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242433#comment-13242433
]

Hadoop QA commented on HADOOP-8227:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520610/HADOOP-8227-trunk.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 5 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/802//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/802//console

This message is automatically generated.

Allow RPC to limit ephemeral port range.

This is a sub task of MAPREDUCE-4079. For security reasons we would like to
limit the range of ports that are used when some RPC servers select a port.

[jira] [Commented] (HADOOP-8232) Provide a command line entry point to view/test topology options

2012-03-30 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242558#comment-13242558
]

Hadoop QA commented on HADOOP-8232:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520625/HADOOP-8232.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/803//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/803//console

This message is automatically generated.

Provide a command line entry point to view/test topology options

[jira] [Commented] (HADOOP-8221) Hftp connections do not have a timeout

2012-03-30 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242577#comment-13242577
]

Hadoop QA commented on HADOOP-8221:
---

-1 overall. Here are the results of testing the latest attachment

http://issues.apache.org/jira/secure/attachment/12520632/HADOOP-8221.branch-1.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/804//console

This message is automatically generated.

Hftp connections do not have a timeout
--

Key: HADOOP-8221
URL: https://issues.apache.org/jira/browse/HADOOP-8221
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 0.23.0, 0.24.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Priority: Critical
Attachments: HADOOP-8221.branch-1.patch, HADOOP-8221.patch

Hftp connections do not have read timeouts. This leads to indefinitely hung
sockets when there is a network outage during which time the remote host
closed the socket.
This may also affect WebHdfs, etc.

[jira] [Commented] (HADOOP-8220) ZKFailoverController doesn't handle failure to become active correctly

2012-03-30 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242673#comment-13242673
]

Hadoop QA commented on HADOOP-8220:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520652/hadoop-8220.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 9 new or modified tests.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/805//console

This message is automatically generated.

ZKFailoverController doesn't handle failure to become active correctly
--

Key: HADOOP-8220
URL: https://issues.apache.org/jira/browse/HADOOP-8220
Project: Hadoop Common
Issue Type: Bug
Components: auto-failover, ha
Affects Versions: 0.23.3, 0.24.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
Attachments: hadoop-8220.txt, hadoop-8220.txt, hadoop-8220.txt,
hadoop-8220.txt, hadoop-8220.txt

The ZKFC doesn't properly handle the case where the monitored service fails
to become active. Currently, it catches the exception and logs a warning, but
then continues on, after calling quitElection(). This causes a NPE when it
later tries to use the same zkClient instance while handling that same
request. There is a test case, but the test case doesn't ensure that the node
that had the failure is later able to recover properly.

[jira] [Commented] (HADOOP-8014) ViewFileSystem does not correctly implement getDefaultBlockSize, getDefaultReplication, getContentSummary

2012-03-30 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242730#comment-13242730
]

Hadoop QA commented on HADOOP-8014:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520663/HADOOP-8014.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 7 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/806//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/806//console

This message is automatically generated.

ViewFileSystem does not correctly implement getDefaultBlockSize,
getDefaultReplication, getContentSummary
-

[jira] [Commented] (HADOOP-8236) haadmin should have configurable timeouts for failover commands

2012-03-30 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242982#comment-13242982
]

Hadoop QA commented on HADOOP-8236:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520711/hadoop-8236.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/807//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/807//console

This message is automatically generated.

haadmin should have configurable timeouts for failover commands
---

[jira] [Commented] (HADOOP-8225) DistCp fails when invoked by Oozie

2012-03-29 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13241467#comment-13241467
 ] 

Hadoop QA commented on HADOOP-8225:
---

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12520465/HADOOP-8225-branch-0.23.1.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/796//console

This message is automatically generated.

 DistCp fails when invoked by Oozie
 --

 Key: HADOOP-8225
 URL: https://issues.apache.org/jira/browse/HADOOP-8225
 Project: Hadoop Common
  Issue Type: Bug
Affects Versions: 0.23.1
Reporter: Mithun Radhakrishnan
 Attachments: HADOOP-8225-branch-0.23.1.patch, HADOOP-8225.patch


 When DistCp is invoked through a proxy-user (e.g. through Oozie), the 
 delegation-token-store isn't picked up by DistCp correctly. One sees failures 
 such as:
 ERROR [main] org.apache.hadoop.tools.DistCp: Couldn't complete DistCp
 operation: 
 java.lang.SecurityException: Intercepted System.exit(-999)
 at
 org.apache.oozie.action.hadoop.LauncherSecurityManager.checkExit(LauncherMapper.java:651)
 at java.lang.Runtime.exit(Runtime.java:88)
 at java.lang.System.exit(System.java:904)
 at org.apache.hadoop.tools.DistCp.main(DistCp.java:357)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:394)
 at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
 at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399)
 at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334)
 at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:147)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at
 org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1177)
 at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:142)
 Looking over the DistCp code, one sees that HADOOP_TOKEN_FILE_LOCATION isn't 
 being copied to mapreduce.job.credentials.binary, in the job-conf. I'll post 
 a patch for this shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8225) DistCp fails when invoked by Oozie

2012-03-29 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13241508#comment-13241508
 ] 

Hadoop QA commented on HADOOP-8225:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12520480/HADOOP-8225.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/797//console

This message is automatically generated.

 DistCp fails when invoked by Oozie
 --

 Key: HADOOP-8225
 URL: https://issues.apache.org/jira/browse/HADOOP-8225
 Project: Hadoop Common
  Issue Type: Bug
Affects Versions: 0.23.1
Reporter: Mithun Radhakrishnan
 Attachments: HADOOP-8225.patch


 When DistCp is invoked through a proxy-user (e.g. through Oozie), the 
 delegation-token-store isn't picked up by DistCp correctly. One sees failures 
 such as:
 ERROR [main] org.apache.hadoop.tools.DistCp: Couldn't complete DistCp
 operation: 
 java.lang.SecurityException: Intercepted System.exit(-999)
 at
 org.apache.oozie.action.hadoop.LauncherSecurityManager.checkExit(LauncherMapper.java:651)
 at java.lang.Runtime.exit(Runtime.java:88)
 at java.lang.System.exit(System.java:904)
 at org.apache.hadoop.tools.DistCp.main(DistCp.java:357)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:394)
 at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
 at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399)
 at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334)
 at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:147)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at
 org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1177)
 at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:142)
 Looking over the DistCp code, one sees that HADOOP_TOKEN_FILE_LOCATION isn't 
 being copied to mapreduce.job.credentials.binary, in the job-conf. I'll post 
 a patch for this shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8221) Hftp connections do not have a timeout

2012-03-29 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13241920#comment-13241920
]

Hadoop QA commented on HADOOP-8221:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520529/HADOOP-8221.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/799//console

This message is automatically generated.

Hftp connections do not have a timeout
--

[jira] [Commented] (HADOOP-8226) a few native libraries are missing from a full build and binary tarball

2012-03-29 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242018#comment-13242018
]

Hadoop QA commented on HADOOP-8226:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520548/HADOOP-8226.patch.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/800//console

This message is automatically generated.

a few native libraries are missing from a full build and binary tarball
---

Key: HADOOP-8226
URL: https://issues.apache.org/jira/browse/HADOOP-8226
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 0.23.1
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik
Attachments: HADOOP-8226.patch.txt

Hadoop 1.0.X ships the following native libraries in its tarball:
{noformat}
hadoop-1.0.1/c++/Linux-amd64-64/lib/libhadooppipes.a
hadoop-1.0.1/c++/Linux-amd64-64/lib/libhadooputils.a
hadoop-1.0.1/c++/Linux-i386-32/lib/libhadooppipes.a
hadoop-1.0.1/c++/Linux-i386-32/lib/libhadooputils.a
hadoop-1.0.1/lib/native/Linux-amd64-64/libhadoop.a
hadoop-1.0.1/lib/native/Linux-i386-32/libhadoop.a
hadoop-1.0.1/c++/Linux-amd64-64/lib/libhdfs.so
hadoop-1.0.1/c++/Linux-i386-32/lib/libhdfs.so
hadoop-1.0.1/lib/native/Linux-amd64-64/libhadoop.so
hadoop-1.0.1/lib/native/Linux-i386-32/libhadoop.so
{noformat}
While Hadoop 0.23.1 ships a subset:
{noformat}
./lib/native/libhadoop.a
./lib/native/libhdfs.a
./lib/native/libhadoop.so
./lib/native/libhdfs.so
{noformat}
The question is: do we have any reason not to support/publish the following
libraries:
libhadooppipes.a, libhadooputils.a ?
And we also used to have librecordio that now seems to be missing from both.
If this is not intentional I can provide a patch to re-enable these bits.

[jira] [Commented] (HADOOP-8220) ZKFailoverController doesn't handle failure to become active correctly

2012-03-29 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13242059#comment-13242059
]

Hadoop QA commented on HADOOP-8220:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520563/hadoop-8220.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 9 new or modified tests.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/801//console

This message is automatically generated.

ZKFailoverController doesn't handle failure to become active correctly
--

[jira] [Commented] (HADOOP-8220) ZKFailoverController doesn't handle failure to become active correctly

2012-03-28 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240792#comment-13240792
]

Hadoop QA commented on HADOOP-8220:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520334/hadoop-8220.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 9 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/793//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/793//console

This message is automatically generated.

ZKFailoverController doesn't handle failure to become active correctly
--

[jira] [Commented] (HADOOP-8149) cap space usage of default log4j rolling policy

2012-03-28 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240803#comment-13240803
]

Hadoop QA commented on HADOOP-8149:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520335/HADOOP-8149.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/794//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/794//console

This message is automatically generated.

cap space usage of default log4j rolling policy

Key: HADOOP-8149
URL: https://issues.apache.org/jira/browse/HADOOP-8149
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Reporter: Patrick Hunt
Assignee: Patrick Hunt
Attachments: HADOOP-8149.patch, HADOOP-8149.patch, HADOOP-8149.patch,
HADOOP-8149.patch, HADOOP-8149.patch

I've seen several critical production issues because logs are not
automatically removed after some time and accumulate. Changes to Hadoop's
default log4j file appender would help with this.
I recommend we move to an appender which:
1) caps the max file size (configurable)
2) caps the max number of files to keep (configurable)
3) uses rolling file appender rather than DRFA, see the warning here:
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/DailyRollingFileAppender.html
Specifically: DailyRollingFileAppender has been observed to exhibit
synchronization issues and data loss.
We'd lose (based on the default log4j configuration) the daily rolling
aspect, however increase reliability.

[jira] [Commented] (HADOOP-8014) ViewFileSystem does not correctly implement getDefaultBlockSize, getDefaultReplication, getContentSummary

2012-03-27 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239867#comment-13239867
]

Hadoop QA commented on HADOOP-8014:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520179/HADOOP-8014.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.TestFilterFileSystem
org.apache.hadoop.ha.TestZKFailoverController

org.apache.hadoop.fs.viewfs.TestViewFileSystemWithAuthorityLocalFileSystem

org.apache.hadoop.fs.viewfs.TestFSMainOperationsLocalFileSystem
org.apache.hadoop.fs.viewfs.TestViewFsTrash
org.apache.hadoop.fs.viewfs.TestViewFileSystemLocalFileSystem
org.apache.hadoop.ha.TestFailoverController

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/791//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/791//console

This message is automatically generated.

ViewFileSystem does not correctly implement getDefaultBlockSize,
getDefaultReplication, getContentSummary
-

[jira] [Commented] (HADOOP-8014) ViewFileSystem does not correctly implement getDefaultBlockSize, getDefaultReplication, getContentSummary

2012-03-27 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239890#comment-13239890
]

Hadoop QA commented on HADOOP-8014:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520183/HADOOP-8014.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.TestFilterFileSystem
org.apache.hadoop.ha.TestZKFailoverController

org.apache.hadoop.fs.viewfs.TestViewFileSystemWithAuthorityLocalFileSystem

org.apache.hadoop.fs.viewfs.TestFSMainOperationsLocalFileSystem
org.apache.hadoop.fs.viewfs.TestViewFileSystemLocalFileSystem
org.apache.hadoop.ha.TestFailoverController

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/792//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/792//console

This message is automatically generated.

ViewFileSystem does not correctly implement getDefaultBlockSize,
getDefaultReplication, getContentSummary
-

[jira] [Commented] (HADOOP-8202) stopproxy() is not closing the proxies correctly

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238713#comment-13238713
]

Hadoop QA commented on HADOOP-8202:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519992/HADOOP-8202-4.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/783//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/783//console

This message is automatically generated.

stopproxy() is not closing the proxies correctly

Key: HADOOP-8202
URL: https://issues.apache.org/jira/browse/HADOOP-8202
Project: Hadoop Common
Issue Type: Bug
Components: ipc
Affects Versions: 0.24.0
Reporter: Hari Mankude
Assignee: Hari Mankude
Priority: Minor
Attachments: HADOOP-8202-1.patch, HADOOP-8202-2.patch,
HADOOP-8202-3.patch, HADOOP-8202-4.patch, HADOOP-8202.patch, HADOOP-8202.patch

I was running testbackupnode and noticed that NNprotocol proxy was not being
closed. Talked with Suresh and he observed that most of the protocols do not
implement ProtocolTranslator and hence the logic in stopproxy() does not
work. Instead, since all of them are closeable, Suresh suggested that
closeable property should be used at close.

[jira] [Commented] (HADOOP-8206) Common portion of ZK-based failover controller

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238741#comment-13238741
]

Hadoop QA commented on HADOOP-8206:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519905/hadoop-8206.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 8 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.ha.TestZKFailoverController

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/784//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/784//artifact/trunk/hadoop-common-project/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/784//console

This message is automatically generated.

Common portion of ZK-based failover controller
--

Key: HADOOP-8206
URL: https://issues.apache.org/jira/browse/HADOOP-8206
Project: Hadoop Common
Issue Type: New Feature
Components: ha
Affects Versions: 0.24.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Attachments: hadoop-8206.txt

This JIRA is for the Common (generic) portion of HDFS-2185. It can't run on
its own, but this JIRA will include unit tests using mock/dummy services.

[jira] [Commented] (HADOOP-8206) Common portion of ZK-based failover controller

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238812#comment-13238812
]

Hadoop QA commented on HADOOP-8206:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520001/hadoop-8206.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 8 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/785//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/785//console

This message is automatically generated.

Common portion of ZK-based failover controller
--

This JIRA is for the Common (generic) portion of HDFS-2185. It can't run on
its own, but this JIRA will include unit tests using mock/dummy services.

[jira] [Commented] (HADOOP-8206) Common portion of ZK-based failover controller

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238974#comment-13238974
]

Hadoop QA commented on HADOOP-8206:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520023/hadoop-8206.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 11 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/786//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/786//console

This message is automatically generated.

Common portion of ZK-based failover controller
--

This JIRA is for the Common (generic) portion of HDFS-2185. It can't run on
its own, but this JIRA will include unit tests using mock/dummy services.

[jira] [Commented] (HADOOP-8216) address log4j.properties inconsistencies btw main and template dirs

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239094#comment-13239094
]

Hadoop QA commented on HADOOP-8216:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520037/HADOOP-8216.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/787//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/787//console

This message is automatically generated.

address log4j.properties inconsistencies btw main and template dirs
---

Key: HADOOP-8216
URL: https://issues.apache.org/jira/browse/HADOOP-8216
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Reporter: Patrick Hunt
Assignee: Patrick Hunt
Priority: Minor
Attachments: HADOOP-8216.patch

DRFAAUDIT is in
./hadoop-common-project/hadoop-common/src/main/packages/templates/conf/log4j.properties
but not in
./hadoop-common-project/hadoop-common/src/main/conf/log4j.properties
(although it's used in hadoop-env.sh)
lesser issues but I noticed:
I see MRAUDIT commented out of main, but it's uncommented in template. (the
conversion pattern also differs).
afaict the other appenders (JSA, MRAUDIT, TLA, etc...) are all still being
used and should not be removed.
Should we be renaming some of these? JSA is being used by the history server
for example.

[jira] [Commented] (HADOOP-8218) RPC.closeProxy shouldn't throw error when closing a mock

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239157#comment-13239157
]

Hadoop QA commented on HADOOP-8218:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520051/hadoop-8218.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/788//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/788//console

This message is automatically generated.

RPC.closeProxy shouldn't throw error when closing a mock

Key: HADOOP-8218
URL: https://issues.apache.org/jira/browse/HADOOP-8218
Project: Hadoop Common
Issue Type: Bug
Components: ipc, test
Affects Versions: 0.24.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
Attachments: hadoop-8218.txt

HADOOP-8202 changed the behavior of RPC.stopProxy() to throw an exception if
called on an object which doesn't implement Closeable. Unfortunately, we use
mock objects in many test cases, and those mocks don't implement Closeable.
This is causing TestZKFailoverController to fail in trunk, for example.

[jira] [Commented] (HADOOP-8220) ZKFailoverController doesn't handle failure to become active correctly

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239178#comment-13239178
]

Hadoop QA commented on HADOOP-8220:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520062/hadoop-8220.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 6 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.ha.TestFailoverController
org.apache.hadoop.ha.TestZKFailoverController

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/789//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/789//console

This message is automatically generated.

ZKFailoverController doesn't handle failure to become active correctly
--

Key: HADOOP-8220
URL: https://issues.apache.org/jira/browse/HADOOP-8220
Project: Hadoop Common
Issue Type: Bug
Components: ha
Affects Versions: 0.23.3, 0.24.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Priority: Critical
Attachments: hadoop-8220.txt

[jira] [Commented] (HADOOP-8218) RPC.closeProxy shouldn't throw error when closing a mock

2012-03-26 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239191#comment-13239191
]

Hadoop QA commented on HADOOP-8218:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520063/hadoop-8218.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 11 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/790//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/790//console

This message is automatically generated.

RPC.closeProxy shouldn't throw error when closing a mock

[jira] [Commented] (HADOOP-8208) Disallow self failover

2012-03-25 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237945#comment-13237945
]

Hadoop QA commented on HADOOP-8208:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519870/hdfs-3145.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/775//console

This message is automatically generated.

Disallow self failover
--

Key: HADOOP-8208
URL: https://issues.apache.org/jira/browse/HADOOP-8208
Project: Hadoop Common
Issue Type: Bug
Components: ha
Reporter: Eli Collins
Assignee: Eli Collins
Attachments: hdfs-3145.txt

It is currently possible for users to make a standby NameNode failover to
itself and become active. We shouldn't allow this to happen in case operators
mistype and miss the fact that there are now two active NNs.
{noformat}
bash-4.1$ hdfs haadmin -ns ha-nn-uri -failover nn2 nn2
Failover from nn2 to nn2 successful
{noformat}
After the failover above, nn2 will be active.

[jira] [Commented] (HADOOP-8208) Disallow self failover

2012-03-25 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237953#comment-13237953
]

Hadoop QA commented on HADOOP-8208:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519870/hdfs-3145.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/776//console

This message is automatically generated.

Disallow self failover
--

Key: HADOOP-8208
URL: https://issues.apache.org/jira/browse/HADOOP-8208
Project: Hadoop Common
Issue Type: Bug
Components: ha
Reporter: Eli Collins
Assignee: Eli Collins
Attachments: hdfs-3145.txt

[jira] [Commented] (HADOOP-8208) Disallow self failover

2012-03-25 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237960#comment-13237960
]

Hadoop QA commented on HADOOP-8208:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519873/hadoop-8208.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/777//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/777//console

This message is automatically generated.

Disallow self failover
--

Key: HADOOP-8208
URL: https://issues.apache.org/jira/browse/HADOOP-8208
Project: Hadoop Common
Issue Type: Bug
Components: ha
Reporter: Eli Collins
Assignee: Eli Collins
Attachments: hadoop-8208.txt, hdfs-3145.txt

[jira] [Commented] (HADOOP-8208) Disallow self failover

2012-03-25 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237966#comment-13237966
]

Hadoop QA commented on HADOOP-8208:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519873/hadoop-8208.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/778//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/778//console

This message is automatically generated.

Disallow self failover
--

[jira] [Commented] (HADOOP-8210) Common side of HDFS-3148

2012-03-25 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238020#comment-13238020
 ] 

Hadoop QA commented on HADOOP-8210:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12519884/hadoop-8210.txt
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/779//console

This message is automatically generated.

 Common side of HDFS-3148
 

 Key: HADOOP-8210
 URL: https://issues.apache.org/jira/browse/HADOOP-8210
 Project: Hadoop Common
  Issue Type: Sub-task
  Components: io, performance
Reporter: Eli Collins
Assignee: Eli Collins
 Attachments: hadoop-8210.txt


 Common side of HDFS-3148, add necessary DNS and NetUtils methods. Test 
 coverage is in the HDFS-3148 patch. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-8211) Update commons-net version to 3.1

2012-03-25 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238027#comment-13238027
]

Hadoop QA commented on HADOOP-8211:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519886/hadoop-8211.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/780//console

This message is automatically generated.

Update commons-net version to 3.1
-

Key: HADOOP-8211
URL: https://issues.apache.org/jira/browse/HADOOP-8211
Project: Hadoop Common
Issue Type: Sub-task
Components: io, performance
Reporter: Eli Collins
Assignee: Eli Collins
Attachments: hadoop-8211.txt

HADOOP-8210 requires the commons-net version be upgraded. Let's bump it to
the latest stable version. The only other user is FtpFs.

[jira] [Commented] (HADOOP-8212) Improve ActiveStandbyElector's behavior when session expires

2012-03-25 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13238113#comment-13238113
]

Hadoop QA commented on HADOOP-8212:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519904/hadoop-8212.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 11 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/781//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/781//console

This message is automatically generated.

Improve ActiveStandbyElector's behavior when session expires

Key: HADOOP-8212
URL: https://issues.apache.org/jira/browse/HADOOP-8212
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 0.23.3, 0.24.0
Reporter: Todd Lipcon
Assignee: Todd Lipcon
Attachments: hadoop-8212.txt

Currently when the ZK session expires, it results in a fatal error being sent
to the application callback. This is not the best behavior -- for example, in
the case of HA, if ZK goes down, we would like the current state to be
maintained, rather than causing either NN to abort. When the ZK clients are
able to reconnect, they should sort out the correct leader based on the
normal locking schemes.

[jira] [Commented] (HADOOP-8204) TestHealthMonitor fails occasionally

2012-03-24 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237753#comment-13237753
]

Hadoop QA commented on HADOOP-8204:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519829/hadoop-8204.txt
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 6 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/773//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/773//console

This message is automatically generated.

TestHealthMonitor fails occasionally
-

Key: HADOOP-8204
URL: https://issues.apache.org/jira/browse/HADOOP-8204
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.3, 0.24.0
Reporter: Tom White
Assignee: Todd Lipcon
Attachments: hadoop-8204.txt, hadoop-8204.txt

See e.g.
https://builds.apache.org/job/PreCommit-HADOOP-Build/756//testReport/org.apache.hadoop.ha/TestHealthMonitor/testMonitor/

[jira] [Commented] (HADOOP-8202) stopproxy() is not closing the proxies correctly

2012-03-24 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237785#comment-13237785
]

Hadoop QA commented on HADOOP-8202:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519847/HADOOP-8202-3.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/774//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/774//console

This message is automatically generated.

stopproxy() is not closing the proxies correctly

[jira] [Commented] (HADOOP-8202) stopproxy() is not closing the proxies correctly

2012-03-23 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236863#comment-13236863
]

Hadoop QA commented on HADOOP-8202:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519670/HADOOP-8202.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/754//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/754//artifact/trunk/hadoop-common-project/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/754//console

This message is automatically generated.

stopproxy() is not closing the proxies correctly

[jira] [Commented] (HADOOP-8202) stopproxy() is not closing the proxies correctly

2012-03-23 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236949#comment-13236949
]

Hadoop QA commented on HADOOP-8202:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519675/HADOOP-8202.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.fs.viewfs.TestViewFsTrash

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/755//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/755//console

This message is automatically generated.

stopproxy() is not closing the proxies correctly

[jira] [Commented] (HADOOP-7030) new topology mapping implementations

2012-03-23 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236960#comment-13236960
]

Hadoop QA commented on HADOOP-7030:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519688/HADOOP-7030.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 4 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.ha.TestHealthMonitor

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/756//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/756//console

This message is automatically generated.

new topology mapping implementations

Key: HADOOP-7030
URL: https://issues.apache.org/jira/browse/HADOOP-7030
Project: Hadoop Common
Issue Type: New Feature
Affects Versions: 0.20.1, 0.20.2, 0.21.0
Reporter: Patrick Angeles
Assignee: Tom White
Attachments: HADOOP-7030-2.patch, HADOOP-7030.patch,
HADOOP-7030.patch, HADOOP-7030.patch, HADOOP-7030.patch, topology.patch

The default ScriptBasedMapping implementation of DNSToSwitchMapping for
determining cluster topology has some drawbacks. Principally, it forks to an
OS-specific script.
This issue proposes two new Java implementations of DNSToSwitchMapping.
TableMapping reads a two column text file that maps an IP or hostname to a
rack ID. Ip4RangeMapping reads a three column text file where each line
represents a start and end IP range plus a rack ID.

[jira] [Commented] (HADOOP-8194) viewfs: quota command does not report remaining quotas

2012-03-23 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236977#comment-13236977
]

Hadoop QA commented on HADOOP-8194:
---

+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519695/HADOOP-8194.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/757//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/757//console

This message is automatically generated.

viewfs: quota command does not report remaining quotas
--

Key: HADOOP-8194
URL: https://issues.apache.org/jira/browse/HADOOP-8194
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.2, 0.23.3, 0.24.0
Reporter: John George
Assignee: John George
Attachments: HADOOP-8194.patch, HADOOP-8194.patch

The space and namesapce quotas and remaining are not reported.

[jira] [Commented] (HADOOP-8202) stopproxy() is not closing the proxies correctly

2012-03-23 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237005#comment-13237005
]

Hadoop QA commented on HADOOP-8202:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519700/HADOOP-8202-1.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac
compiler warnings.

+1 eclipse:eclipse. The patch built with eclipse:eclipse.

+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

+1 contrib tests. The patch passed contrib unit tests.

Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/758//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/758//console

This message is automatically generated.

stopproxy() is not closing the proxies correctly

[jira] [Commented] (HADOOP-8088) User-group mapping cache incorrectly does negative caching on transient failures

2012-03-23 Thread Hadoop QA (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/HADOOP-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237215#comment-13237215
 ] 

Hadoop QA commented on HADOOP-8088:
---

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12518767/hadoop-8088-trunk.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 3 new or modified tests.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/760//console

This message is automatically generated.

 User-group mapping cache incorrectly does negative caching on transient 
 failures
 

 Key: HADOOP-8088
 URL: https://issues.apache.org/jira/browse/HADOOP-8088
 Project: Hadoop Common
  Issue Type: Bug
  Components: security
Affects Versions: 0.20.205.0, 1.0.0, 1.1.0, 0.23.1, 0.24.0
Reporter: Kihwal Lee
 Fix For: 1.0.2, 0.23.2, 0.24.0

 Attachments: hadoop-8088-branch-1.patch, hadoop-8088-branch-1.patch, 
 hadoop-8088-trunk.patch, hadoop-8088-trunk.patch, hadoop-8088-trunk.patch


 We've seen a case where some getGroups() calls fail when the ldap server or 
 the network is having transient failures. Looking at the code, the 
 shell-based and the JNI-based implementations swallow exceptions and return 
 an empty or partial list. The caller, Groups#getGroups() adds this likely 
 empty list into the mapping cache for the user. This will function as 
 negative caching until the cache expires. I don't think we want negative 
 caching here, but even if we do, it should be intelligent enough to 
 distinguish transient failures from ENOENT. The log message in the jni-based 
 impl also needs an improvement. It should print what exception it encountered 
 instead of just saying one happened.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HADOOP-7689) Process cannot exit when there is many RPC readers more that actual client

2012-03-23 Thread Hadoop QA (Commented) (JIRA)

[
https://issues.apache.org/jira/browse/HADOOP-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237219#comment-13237219
]

Hadoop QA commented on HADOOP-7689:
---

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12517661/HADOOP-7689.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 patch. The patch command could not apply the patch.

Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/761//console

This message is automatically generated.

Process cannot exit when there is many RPC readers more that actual client
--

Key: HADOOP-7689
URL: https://issues.apache.org/jira/browse/HADOOP-7689
Project: Hadoop Common
Issue Type: Bug
Components: ipc
Affects Versions: 0.21.0
Environment: local
Reporter: Denny Ye
Labels: rpc
Attachments: HADOOP-7689.patch

I met a strange issue that process cannot exit when I run RPC test cases in
my Eclipse.
Conditions:
1. Only one Server and one client(local)
2. I have set many readers(conf.setInt(ipc.server.read.threadpool.size,
5)), it great than client number.
After any test cases, the process cannot exit. I tested with several cases
and found the root cause.
RPC serves socket with reader(transferring binary to Call), and even shutdown
the thread pool. But all the free readers are blocked at
readSelector.select() (they are useless by Listener)
Those threads and process cannot exit always.
It can be fixed by invoking corresponding selector for each reader.The same
thing was done at 0.20 version.

1 2 3 4 5 6 >

1 - 100 of 576 matches

Mail list logo