ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonenko Alexander (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-9950) YARN RM HA Mode Configurations Are Incorrect
Date Fri, 06 Mar 2015 01:36:39 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-9950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Antonenko Alexander updated AMBARI-9950:
----------------------------------------
    Attachment: AMBARI-9950.patch

> YARN RM HA Mode Configurations Are Incorrect
> --------------------------------------------
>
>                 Key: AMBARI-9950
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9950
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9950.patch
>
>
> When enabling YARN RM HA mode, it doesn't appear as though we are creating the additional
{{yarn-site}} properties correctly. Consider that we do create the following:
> {noformat}
> "yarn.resourcemanager.ha.automatic-failover.zk-base-path" : "/yarn-leader-election",
> "yarn.resourcemanager.ha.enabled" : "true",
> "yarn.resourcemanager.ha.rm-ids" : "rm1,rm2",
> "yarn.resourcemanager.hostname" : "c6402.ambari.apache.org",
> "yarn.resourcemanager.hostname.rm1" : "c6402.ambari.apache.org",
> "yarn.resourcemanager.hostname.rm2" : "c6403.ambari.apache.org",
> "yarn.resourcemanager.webapp.address" : "c6402.ambari.apache.org:8088",
> "yarn.resourcemanager.webapp.https.address" : "c6402.ambari.apache.org:8090”,
> {noformat}
> You can see that we have created aliases (rm1 and rm2) and created some dynamic keys
for these hosts, such as {{yarn.resourcemanager.hostname.rm1}}
> However, the {{yarn-site}} documentation states that other properties, such as the web
address, need to also be specified in a similar manner. Otherwise, how does YARN know which
port to spin up the RM on each host?
> {noformat:title=Missing Properties}
> yarn.resourcemanager.webapp.address.rm1
> yarn.resourcemanager.webapp.address.rm2
> yarn.resourcemanager.webapp.https.address.rm1
> yarn.resourcemanager.webapp.https.address.rm2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message