ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8724) Rolling Upgrade - Upgrade Pack to restart standby ResourceManager first, failover, and then upgrade the remaining RM
Date Wed, 17 Dec 2014 18:10:13 GMT

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

Alejandro Fernandez commented on AMBARI-8724:
---------------------------------------------

[~ncole]
In MasterHostResolver, if pair is null, it could have failed for various reasons, even in
HA mode. I believe we should only set a single master in the else clause if we know Namenode
is not in HA (i.e., the size of the hosts is 1). Thoughts?
{code}
+          } else {
+            hostsType.master = componentHosts.iterator().next();
           }
{code}

Thanks for generalizing it to queryJmxBeanValue(), looks much cleaner!

> Rolling Upgrade - Upgrade Pack to restart standby ResourceManager first, failover, and
then upgrade the remaining RM
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8724
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8724
>             Project: Ambari
>          Issue Type: Technical task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Nate Cole
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8724.patch
>
>
> Runbook outlines that RM needs to first upgrade the standby, then failover to make the
upgrade standby the active, and then upgrade the RM that is now the standby.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message