[
https://issues.apache.org/jira/browse/YARN-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993759#comment-13993759
]
Karthik Kambatla commented on YARN-2036:
----------------------------------------
Thanks Ray. Comments:
# This is not entirely correct. One can choose to set
yarn.resourcemanager.address in addition to setting
yarn.resourcemanager.hostname to override the actual host:port used.
{noformat}
Should only be set if <<<yarn.resourcemanager.hostname>>> is not set.
{noformat}
# May be, we should add this after the *.address configs. And, the text should
probably say something along the lines of - "As an alternative to setting each
*.address config, ..."
{code]
+| <<<yarn.resourcemanager.hostname>>> | | |
+| | <<<ResourceManager>>> host. | |
+| | | <host>\ |
+| | | Replaces the host part of all earlier
<<<yarn.resourcemanager.*.address>>> resources. Results in default ports for
ResourceManager components. |
{code}
# Nit: yarn.resourcemanager.*.address excludes yarn.resourcemanager.address :)
> Document yarn.resourcemanager.hostname in ClusterSetup
> ------------------------------------------------------
>
> Key: YARN-2036
> URL: https://issues.apache.org/jira/browse/YARN-2036
> Project: Hadoop YARN
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.4.0
> Reporter: Karthik Kambatla
> Assignee: Ray Chiang
> Priority: Minor
> Fix For: 2.5.0
>
> Attachments: YARN2036-01.patch, YARN2036-02.patch
>
>
> ClusterSetup doesn't talk about yarn.resourcemanager.hostname - most people
> should just be able to use that directly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
