hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1660) add the ability to set yarn.resourcemanager.hostname.rm-id instead of setting all the various host:port properties for RM
Date Tue, 28 Jan 2014 22:05:33 GMT

    [ https://issues.apache.org/jira/browse/YARN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884758#comment-13884758
] 

Arpit Gupta commented on YARN-1660:
-----------------------------------

nope yarn-site should only have

{code}
<property>
        <name>yarn.resourcemanager.hostname.rm1</name>
        <value>196.128.1.1</value>
    </property>
<property>
        <name>yarn.resourcemanager.hostname.rm2</name>
        <value>196.128.1.2</value>
    </property>
{code}

All of the other properties mentioned in https://issues.apache.org/jira/browse/YARN-1660?focusedCommentId=13883658&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13883658
should use the hostnames specified above and pick the appropriate ports for the defaults.
We should not need to specify any other hostname property related to RM.

> add the ability to set yarn.resourcemanager.hostname.rm-id instead of setting all the
various host:port properties for RM
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1660
>                 URL: https://issues.apache.org/jira/browse/YARN-1660
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Arpit Gupta
>            Assignee: Xuan Gong
>
> Currently the user has to specify all the various host:port properties for RM. We should
follow the pattern that we do for non HA setup where we can specify yarn.resourcemanager.hostname.rm-id
and the defaults are used for all other affected properties.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message