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

Hadoop QA commented on AMBARI-21619:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12879722/AMBARI-21619.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

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

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  org.apache.ambari.server.agent.TestHeartbeatHandler
                  org.apache.ambari.server.state.UpgradeHelperTest

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11903//console

This message is automatically generated.

> More ResourceManager HA host group placeholders in blueprints
> -------------------------------------------------------------
>
>                 Key: AMBARI-21619
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21619
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Doroszlai, Attila
>            Assignee: Doroszlai, Attila
>             Fix For: trunk, 2.5.3
>
>         Attachments: AMBARI-21619.patch
>
>
> Some ResourceManager HA addresses are not replaced during blueprint 
> processing (cluster creation, export).  This may cause failure of starting 
> ResourceManager, or force user to enter specific host names in the blueprint 
> as a workaround.
> {noformat:title=/usr/hdp/current/hadoop-client/conf/yarn-site.xml}
>     <property>
>       <name>yarn.resourcemanager.address.rm1</name>
>       <value>%HOSTGROUP::master0%:8050</value>
>     </property>
>     <property>
>       <name>yarn.resourcemanager.address.rm2</name>
>       <value>%HOSTGROUP::master1%:8050</value>
>     </property>
>     <property>
>       <name>yarn.resourcemanager.admin.address.rm1</name>
>       <value>%HOSTGROUP::master0%:8141</value>
>     </property>
>     <property>
>       <name>yarn.resourcemanager.admin.address.rm2</name>
>       <value>%HOSTGROUP::master1%:8141</value>
>     </property>
>     <property>
>       <name>yarn.resourcemanager.resource-tracker.address.rm1</name>
>       <value>%HOSTGROUP::master0%:8025</value>
>     </property>
>     <property>
>       <name>yarn.resourcemanager.resource-tracker.address.rm2</name>
>       <value>%HOSTGROUP::master1%:8025</value>
>     </property>
>     <property>
>       <name>yarn.resourcemanager.scheduler.address.rm1</name>
>       <value>%HOSTGROUP::master0%:8030</value>
>     </property>
>     <property>
>       <name>yarn.resourcemanager.scheduler.address.rm2</name>
>       <value>%HOSTGROUP::master1%:8030</value>
>     </property>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to