[
https://issues.apache.org/jira/browse/HBASE-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687181#comment-13687181
]
Andrew Purtell commented on HBASE-8453:
---------------------------------------
This is the familiar pattern:
bq. I've applied this patch against trunk and run in an EC2 vm (Linux
ip-10-152-187-175 2.6.32-276.el6.x86_64 #1 SMP Tue May 29 17:38:19 EDT 2012
x86_64 x86_64 x86_64 GNU/Linux, ami-89ad18e0, jdk-7u21-linux-x64). The test
passes on both hadoop1 and hadoop2 profiles.
and
bq. The 0.94 patch applies cleanly and runs just fine for both hadoop1 and
hadoop2 profiles on the same VM.
But then we have this:
bq. produced this [build
error|https://builds.apache.org/job/HBase-0.94-security/169/] on 0.94-security.
A worse result than before. Not confined to EC2.
Let's revert the patch and close this issue definitively.
I propose instead we move MiniMRCluster instantiation and JobConf building and
its gory details to the hadoop-compat modules. A simple consistent approach
remains elusive.
> TestImportExport failing again due to configuration issues
> ----------------------------------------------------------
>
> Key: HBASE-8453
> URL: https://issues.apache.org/jira/browse/HBASE-8453
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce, test
> Affects Versions: 0.98.0, 0.94.8, 0.95.1
> Reporter: Andrew Purtell
> Fix For: 0.98.0, 0.95.2, 0.94.9
>
> Attachments: 8453.patch, 8453.patch, 8453-v1-0.94.patch
>
>
> TestImportExport fails for me with a connection refused exception:
> {noformat}
> 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:162)
> at
> org.apache.hadoop.yarn.client.YarnClientImpl.getNewApplication(YarnClientImpl.java:121)
> at
> org.apache.hadoop.mapred.ResourceMgrDelegate.getNewJobID(ResourceMgrDelegate.java:107)
> at org.apache.hadoop.mapred.YARNRunner.getNewJobID(YARNRunner.java:231)
> at
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:352)
> [...]
> Caused by: com.google.protobuf.ServiceException: java.net.ConnectException:
> Call From ip-10-174-75-236/10.174.75.236 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
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:212)
> at com.sun.proxy.$Proxy89.getNewApplication(Unknown Source)
> at
> org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getNewApplication(ClientRMProtocolPBClientImpl.java:159)
> ... 42 more
> {noformat}
> Settings in the MiniMRCluster configuration are not properly propagated in
> this test.
--
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
