Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.5.2
-
None
Description
Some ResourceManager HA addresses are not replaced during blueprint processing (cluster creation, export). This may cause failure of starting ResourceManager, or force user to enter specific host names in the blueprint as a workaround.
/usr/hdp/current/hadoop-client/conf/yarn-site.xml
<property> <name>yarn.resourcemanager.address.rm1</name> <value>%HOSTGROUP::master0%:8050</value> </property> <property> <name>yarn.resourcemanager.address.rm2</name> <value>%HOSTGROUP::master1%:8050</value> </property> <property> <name>yarn.resourcemanager.admin.address.rm1</name> <value>%HOSTGROUP::master0%:8141</value> </property> <property> <name>yarn.resourcemanager.admin.address.rm2</name> <value>%HOSTGROUP::master1%:8141</value> </property> <property> <name>yarn.resourcemanager.resource-tracker.address.rm1</name> <value>%HOSTGROUP::master0%:8025</value> </property> <property> <name>yarn.resourcemanager.resource-tracker.address.rm2</name> <value>%HOSTGROUP::master1%:8025</value> </property> <property> <name>yarn.resourcemanager.scheduler.address.rm1</name> <value>%HOSTGROUP::master0%:8030</value> </property> <property> <name>yarn.resourcemanager.scheduler.address.rm2</name> <value>%HOSTGROUP::master1%:8030</value> </property>
Attachments
Attachments
Issue Links
- links to