Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 19 Aug 2016 20:02:20 +0000 (UTC)
From: "Nate Cole (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12998528.1471624582000.358156.1471636940454@Atlassian.JIRA>
In-Reply-To: <JIRA.12998528.1471624582000@Atlassian.JIRA>
References: <JIRA.12998528.1471624582000@Atlassian.JIRA> <JIRA.12998528.1471624582731@arcas>
Subject: [jira] [Updated] (AMBARI-18216) Both NameNodes reporting version
 mismatches before Finalizing RU
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 19 Aug 2016 20:02:22 -0000


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

Nate Cole updated AMBARI-18216:
-------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

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