ResourceManager Not Listening on All Interfaces when "Bind ResourceManager to Wildcard Address" is set BDA V4.2/CDH5.4
(Doc ID 2032401.1)
Last updated on JANUARY 18, 2019
Applies to:Big Data Appliance Integrated Software - Version 4.2.0 and later
On BDA V4.2/CDH 5.4 the ResourceManager (RM) is observed not to be listening on all interfaces even though the Cloudera Manager (CM) configuration parameter "Bind ResourceManager to Wildcard Address" is enabled. The RM is found to be listening only over the InfiniBand addresses. Not listening on all interfaces prevents access from clients that connect externally and run jobs, such as spark-shell, etc. as they do not go over the InfiniBand network.
1. In Cloudera Manager "Bind ResourceManager to Wildcard Address" is set. In CM navigate:
Home > yarn > Configuration > Search for: "Bind ResourceManager to Wildcard Address"
Observe that it is enabled allowing the RM to listen on all of its ports:
2. On the Active RM node (typically Node 3 or Node 4 but verify in CM yarn > Instances) the RM ports listen on the IB network:
See the RM ports 8030, 8031, 8032, 8033 listening on the IB network:
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