You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2016/08/19 16:52:20 UTC

[jira] [Updated] (AMBARI-18216) Both NameNodes reporting version mismatches before Finalizing RU

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

Nate Cole updated AMBARI-18216:
-------------------------------
    Summary: Both NameNodes reporting version mismatches before Finalizing RU  (was: RU: Both NameNodes reporting version mismatches before Finalizing RU)

> 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
>
>
> 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)