[
https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza updated YARN-458:
----------------------------
Description:
The YARN resourcemanager's address is included in four different configs:
yarn.resourcemanager.scheduler.address,
yarn.resourcemanager.resource-tracker.address, yarn.resourcemanager.address,
and yarn.resourcemanager.admin.address
A new user trying to configure a cluster needs to know the names of all these
four configs.
The same issue exists for nodemanagers.
It would be much easier if they could simply specify
yarn.resourcemanager.hostname and yarn.nodemanager.hostname and default ports
for the other ones would kick in.
was:
The YARN resourcemanager's address is included in four different configs:
yarn.resourcemanager.scheduler.address,
yarn.resourcemanager.resource-tracker.address, yarn.resourcemanager.address,
and yarn.resourcemanager.admin.address
A new user trying to configure a cluster needs to know the names of all these
four configs.
It would be much easier if they could simply specify
yarn.resourcemanager.address and default ports for the other ones would kick in.
> YARN daemon addresses must be placed in many different configs
> --------------------------------------------------------------
>
> Key: YARN-458
> URL: https://issues.apache.org/jira/browse/YARN-458
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-458.patch
>
>
> The YARN resourcemanager's address is included in four different configs:
> yarn.resourcemanager.scheduler.address,
> yarn.resourcemanager.resource-tracker.address, yarn.resourcemanager.address,
> and yarn.resourcemanager.admin.address
> A new user trying to configure a cluster needs to know the names of all these
> four configs.
> The same issue exists for nodemanagers.
> It would be much easier if they could simply specify
> yarn.resourcemanager.hostname and yarn.nodemanager.hostname and default ports
> for the other ones would kick in.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
