[
https://issues.apache.org/jira/browse/AMBARI-18216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428895#comment-15428895
]
Hudson commented on AMBARI-18216:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5557 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5557/])
AMBARI-18216. Both NameNodes reporting version mismatches before (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4773c839965068bb2827b0d308c0bec9599b39c1])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/utils/HTTPUtils.java
> Both NameNodes reporting version mismatches before Finalizing RU
> ----------------------------------------------------------------
>
> Key: AMBARI-18216
> URL: https://issues.apache.org/jira/browse/AMBARI-18216
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18216.patch
>
>
> When doing RU on a secured cluster, the MasterHostResolver class is failing
> the lookup of JMX. Ambari's SSL configuration must be used just like metrics
> do.
> Also adding some logging, and making sure that if we have 2 confirmed NN,
> that we are always picking one to be the active and one to be the standby.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
