[
https://issues.apache.org/jira/browse/AMBARI-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302844#comment-14302844
]
Hadoop QA commented on AMBARI-9289:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696066/AMBARI-9289.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 9 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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1558//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1558//console
This message is automatically generated.
> RU - Fix hardcoded Namenode address and JMX port
> ------------------------------------------------
>
> Key: AMBARI-9289
> URL: https://issues.apache.org/jira/browse/AMBARI-9289
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.0.0
>
> Attachments: AMBARI-9289.patch
>
>
> Java-side:
> UpgradeHelper hardcodes the JMX port number when figuring out the active and
> standby namenodes.
> Python-side:
> When using HA mode, the JMX URLs for NameNode must be taken from
> dfs.namenode.http-address.<cluster>.<nn#>
> See journalnode_upgrade.py
> E.g.,
> dfs.namenode.http-address.ha.nn1 : c6405.ambari.apache.org:50070
> dfs.namenode.http-address.ha.nn2 : c6403.ambari.apache.org:50070
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
