[
https://issues.apache.org/jira/browse/HBASE-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436948#comment-13436948
]
Hadoop QA commented on HBASE-6601:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12541388/HBASE-6601-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 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).
-1 findbugs. The patch appears to introduce 9 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.hbase.master.TestSplitLogManager
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2606//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2606//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2606//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2606//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2606//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2606//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2606//console
This message is automatically generated.
> TestImportExport failing against Hadoop 2
> -----------------------------------------
>
> Key: HBASE-6601
> URL: https://issues.apache.org/jira/browse/HBASE-6601
> Project: HBase
> Issue Type: Bug
> Reporter: Scott Forman
> Attachments: HBASE-6601-0.94.patch, HBASE-6601-trunk.patch
>
>
> TestImportExport.testSimpleCase is failing with the following exception:
> java.lang.reflect.UndeclaredThrowableException
> at
> org.apache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPBImpl.unwrapAndThrowException(YarnRemoteExceptionPBImpl.java:135)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getNewApplication(ClientRMProtocolPBClientImpl.java:134)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.getNewJobID(ResourceMgrDelegate.java:181)
> at org.apache.hadoop.mapred.YARNRunner.getNewJobID(YARNRunner.java:214)
> at
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:337)
> at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1216)
> at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1213)
> 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:1332)
> at org.apache.hadoop.mapreduce.Job.submit(Job.java:1213)
> at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1234)
> at
> org.apache.hadoop.hbase.mapreduce.TestImportExport.testSimpleCase(TestImportExport.java:114)
> ....
> Caused by: com.google.protobuf.ServiceException: java.net.ConnectException:
> Call From asurus.iridiant.net/50.23.172.109 to 0.0.0.0:8032 failed on
> connection exception: java.net.ConnectException: Connection refused; For more
> details see: http://wiki.apache.org/hadoop/ConnectionRefused
> ============================================================================
> The problem is that a connection to the YARN resource manager is being made
> at the default address (0.0.0.0:8032) instead of the actual address that it
> is listening on.
> This test creates two mini clusters, one for map reduce and one for hbase.
> The Configuration for the map reduce mini cluster has the correct resource
> manager address, while the Configuration for the hbase mini cluster has the
> default resource manager address, and the test is using only the
> Configuration from the hbase mini cluster.
--
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
