hadoop - YARN Application Master unable to connect to Resource Manager -
i have 4 node cluster (1 namenode/resource manager 3 datanodes/node managers)
i trying run simple tez example orderedwordcount
hadoop jar c:\hdp\tez-0.4.0.2.1.1.0-1621\tez-mapreduce-examples-0.4.0.2.1.1.0-1621.jar orderedwordcount sample/test.txt /sample/out
the job gets accepted ,the application master , container gets setup on nodemanager see these logs
2014-09-10 17:53:31,982 info [servicethread:org.apache.tez.dag.app.rm.taskschedulereventhandler] org.apache.hadoop.yarn.client.rmproxy: connecting resourcemanager @ /0.0.0.0:8030
2014-09-10 17:53:34,060 info [servicethread:org.apache.tez.dag.app.rm.taskschedulereventhandler] org.apache.hadoop.ipc.client: retrying connect server: 0.0.0.0/0.0.0.0:8030. tried 0 time(s); retry policy retryuptomaximumcountwithfixedsleep(maxretries=10, sleeptime=1000 milliseconds)
after configurable timeout job fails
i searched problem , pointed yarn.resourcemanager.scheduler.address configuration. in resource manager node , node managers have configuration defined correctly reason not getting picked up
<property> <name>yarn.resourcemanager.hostname</name> <value>10.234.225.69</value> </property> <property> <name>yarn.resourcemanager.address</name> <value>${yarn.resourcemanager.hostname}:8032</value> </property> <property> <name>yarn.resourcemanager.webapp.address</name> <value>${yarn.resourcemanager.hostname}:8088</value> </property> <property> <name>yarn.resourcemanager.scheduler.address</name> <value>${yarn.resourcemanager.hostname}:8030</value> </property> <property> <name>yarn.resourcemanager.resource-tracker.address</name> <value>${yarn.resourcemanager.hostname}:8031</value> </property> <property> <name>yarn.resourcemanager.admin.address</name> <value>${yarn.resourcemanager.hostname}:8033</value> </property>
it might possible resourcemanager listening on ipv6 port while worker nodes (i.e nodemanagers) might using ipv4 connect resourcemanager
to check if case, a
netstat -aln | grep 8030
if similar :::8030
, resourcemanager indeed listening on ipv6 port. if ipv4 port, should see similar 0.0.0.0:8030
to fix this, might want consider disabling ipv6 on machines , try once again.
Comments
Post a Comment