After Node 3 Migration Both Resource Managers in Standby because yarn-site.xml on the Non-Migrated Resource Manager Incorrectly References Node 3
(Doc ID 2525921.1)
Last updated on NOVEMBER 08, 2019
Applies to:Big Data Appliance Integrated Software - Version 4.11.0 and later
In the example here Node 3 is migrated to Node 5.
By default the BDA has ResourceManager(RM) roles on Node 3 and Node 4.
In the case here after migrating Node 3 to another host, for example, Node 5, the Resource Manager yarn-site.xml file on the non-migrated Resource Manager, e.g. Node 4, incorrectly retains references to Node 3.
Because the yarn-site.xml on the non-migrated Resource Manager e.g. Node 4, references Node 3 and not the node with migrated roles, e.g. Node 5:
- Both Resource Managers are in Standby.
- Zookeeper will not start on all hosts.
This can be seen on the yarn-site.xml on Node 4 as below.
1. On Node 4 navigate to the most recent yarn-RESOURCEMANAGER directory under /var/run/cloudera-scm-agent/process.
In both examples above the reference to <HOSTNAME3> should be the migrated host <HOSTNAME5>.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document