It seems like the AM is binding to the external/public hostname and not the internal IP.
Could you look for this log message in the AM logs: "Instantiated DAGClientRPCServer at”. This will provide some information as to what the AM is binding to. thanks — Hitesh On Aug 11, 2014, at 7:43 AM, Johannes Zillmann <jzillm...@googlemail.com> wrote: > Hey guys, > > having a test-infrastructure for Hadoop on ec2. The client sits usually > outside of ec2. > Using plain map-reduce on YARN everything works fine. > Using Tez i run into following exception: > > INFO [2014-07-29 00:09:06.653] [MrPlanRunnerV2] (TezClient.java:507) - Failed > to retrieve AM Status via proxy > com.google.protobuf.ServiceException: > org.apache.hadoop.net.ConnectTimeoutException: Call From > ip-10-73-6-154.ec2.internal/10.73.6.154 to > ec2-54-81-245-144.compute-1.amazonaws.com:60914 failed on socket timeout > exception: org.apache.hadoop.net.ConnectTimeoutException: connect timed out; > For more details see: http: > //wiki.apache.org/hadoop/SocketTimeout > > at > org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:216) > at com.sun.proxy.$Proxy116.getAMStatus(Unknown Source) > at > org.apache.tez.client.TezClient.getAppMasterStatus(TezClient.java:500) > at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:586) > > > I could resolve the problem for Tez changing the hostname of the instances to > their public dns’. However, that is causing problems with other components. > Do you know of any place in Tez which is related to that ? Any tweak which > could make chaining the hostname superfluous ? > > best > Johannes
