Arpit Agarwal created YARN-1994:
-----------------------------------
Summary: Expose YARN/MR endpoints on multiple interfaces
Key: YARN-1994
URL: https://issues.apache.org/jira/browse/YARN-1994
Project: Hadoop YARN
Issue Type: Improvement
Components: nodemanager, resourcemanager, webapp
Affects Versions: 2.4.0
Reporter: Arpit Agarwal
YARN and MapReduce daemons currently do not support specifying a wildcard
address for the server endpoints. This prevents the endpoints from being
accessible from all interfaces on a multihomed machine.
A preliminary shows the following candidates:
# yarn.nodemanager.address
# yarn.nodemanager.webapp.address
# yarn.nodemanager.webapp.https.address
# yarn.resourcemanager.address
# yarn.resourcemanager.webapp.address
# yarn.resourcemanager.webapp.https.address
# yarn.resourcemanager.resource-tracker.address
# yarn.resourcemanager.scheduler.address
# yarn.resourcemanager.admin.address
# mapreduce.jobhistory.address
Note that if we do specify INADDR_ANY for any of the options, it will break
clients as they will attempt to connect to 0.0.0.0. We need a solution that
allows specifying a hostname or IP-address for clients while requesting
wildcard bind for the servers.
# mapreduce.jobhistory.admin.address
# mapreduce.jobhistory.webapp.address
# mapreduce.jobhistory.webapp.https.address
# mapreduce.history.server.http.address (Deprecated)
# yarn.timeline-service.webapp.address
# yarn.timeline-service.webapp.https.address
--
This message was sent by Atlassian JIRA
(v6.2#6252)
