[
https://issues.apache.org/jira/browse/HBASE-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465203#comment-13465203
]
stack commented on HBASE-6601:
------------------------------
When I ran this local with hadoop.profile=2.0, I get this... same as we see in
hbase builds up on hadoop 2.0:
https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/194/#showFailuresLink
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.hadoop.hbase.mapreduce.TestImportExport
2012-09-27 15:57:27.192 java[62016:1903] Unable to load realm info from
SCDynamicStore
2012-09-27 15:57:27.325 java[62016:1903] Unable to load realm info from
SCDynamicStore
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 46.22 sec <<<
FAILURE!
Results :
Tests in error:
testSimpleCase(org.apache.hadoop.hbase.mapreduce.TestImportExport):
java.lang.RuntimeException: java.util.zip.ZipException: duplicate entry:
META-INF/MANIFEST.MF
testMetaExport(org.apache.hadoop.hbase.mapreduce.TestImportExport):
java.lang.RuntimeException: java.util.zip.ZipException: duplicate entry:
META-INF/MANIFEST.MF
{code}
These is work to do here still?
> 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-changeFunctSign.patch,
> HBASE-6601-0.94.patch, HBASE-6601-0.94.patch,
> HBASE-6601-trunk-changeFunctSign.patch,
> HBASE-6601-trunk-changeFunctSign.patch, HBASE-6601-trunk.patch,
> HBASE-6601-trunk.patch, HBASE-6601-trunk.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 miniclusters, one for map reduce and one for hbase, and
> each minicluster has its own Configuration. The Configuration for the map
> reduce minicluster has the correct resource manager address, while the
> Configuration for the hbase minicluster has the default resource manager
> address. Since the test is using only the Configuration from the hbase
> minicluster, it sees the default address for the resource manager, instead of
> the actual address.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
