ambari-dev mailing list archives

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

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

Hadoop QA commented on AMBARI-9950:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12702952/AMBARI-9950.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1942//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1942//console

This message is automatically generated.

> 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