Reply To: hadoop 2.6 installation/setup, hdfs ok, yarn/mapred usaly fail but sometime ok

look same issue on 2.3.0 hadoop

http://comments.gmane.org/gmane.comp.jakarta.lucene.hadoop.user/47539

yarn-site.xml extract

<property>
<name>yarn.resourcemanager.hostname</name>
<value>stargate</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}:8025</value>
<description>ResourceManager host:port for NodeManagers. If set, overrides the hostname set in yarn.resourcemanager.hostname.</description>
</property>
<property>
<name>yarn.resourcemanager.address</name>
<value>${yarn.resourcemanager.hostname}:8032</value>
</property>

call url on my cluster for check configuration, expression variable est generated

http://192.168.0.11:8088/conf

<property>
<name>yarn.resourcemanager.scheduler.address</name>
<value>stargate:8030</value>
<source>programatically</source>
</property>

<property>
<name>yarn.resourcemanager.address</name>
<value>stargate:8032</value>
<source>programatically</source>
</property>

job.xml created by container on slave node, we can see some property with $yarn.resourcemanager.hostname are not evaluate correctly and some other properties are done correctly

job.xml:<property><name>yarn.resourcemanager.scheduler.address</name><value>${yarn.resourcemanager.hostname}:8030</value><source>yarn-default.xml</source></property>

here we can see correct evaluation value

job.xml:<property><name>yarn.resourcemanager.address</name><value>stargate:8032</value><source>programatically</source></property>