[
https://issues.apache.org/jira/browse/HBASE-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684429#comment-13684429
]
Andrew Purtell commented on HBASE-8453:
---------------------------------------
MR tests complete for both Hadoop 1 and 2 - except for on EC2. I do not know
definitively why Hadoop 1's MiniMRCluster becomes unhappy on EC2 with this
change. I could guess (similar to Jon's rumination) but that wouldn't add
anything. This change appears to solve MR related test issues everywhere for
Hadoop 2 without special casing YARN internal configs bound to change at every
release. The downside is a test only quirk (this is the MRMiniCluster's problem
- not a real MR issue on a real deploy) with Hadoop 1 on EC2.
I'm fine with holding off on committing this until someone can find the time to
dump configs at every step and eyeball them. Not sure when I'll have that time
personally. Thought I'd ping here again since I found another place where this
fixes Hadoop 2 issues today. (And I no longer care about Hadoop 1.)
> 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-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
