Return-Path: 
 <dev-return-51296-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-dev-archive@www.apache.org
Delivered-To: apmail-ambari-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8DEC610FA8
	for <apmail-ambari-dev-archive@www.apache.org>;
 Tue, 16 Dec 2014 22:33:14 +0000 (UTC)
Received: (qmail 82839 invoked by uid 500); 16 Dec 2014 22:33:13 -0000
Delivered-To: apmail-ambari-dev-archive@ambari.apache.org
Received: (qmail 82742 invoked by uid 500); 16 Dec 2014 22:33:13 -0000
Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ambari.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ambari.apache.org>
List-Post: <mailto:dev@ambari.apache.org>
List-Id: <dev.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list dev@ambari.apache.org
Received: (qmail 82538 invoked by uid 99); 16 Dec 2014 22:33:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2014 22:33:13 +0000
Date: Tue, 16 Dec 2014 22:33:13 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12761873.1418680755000.38487.1418769193481@Atlassian.JIRA>
In-Reply-To: <JIRA.12761873.1418680755000@Atlassian.JIRA>
References: <JIRA.12761873.1418680755000@Atlassian.JIRA>
 <JIRA.12761873.1418680755776@arcas>
Subject: [jira] [Commented] (AMBARI-8724) Rolling Upgrade - Upgrade Pack to
 restart standby ResourceManager first, failover, and then upgrade the
 remaining RM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Jonathan Hurley commented on AMBARI-8724:
-----------------------------------------

+1 - I have comments b/c I'm confused and don't fully understand the system yet and want to make sure what I'm seeing isn't a boog.

{noformat}
-          <task xsi:type="execute">
+          <task xsi:type="execute" hosts="master">
{noformat}
- Can this be hosts="active" maybe? It's a little confusing; makes it seem like you're saying "Run it on all masters" when I think we're saying "Run it only on the main master (ignoring others in standby".

{noformat}
            // !!! revisit if needed
            if (hostsType.master != null && hostsType.secondary != null) {
{noformat}
- Should this be secondary? I would think that a secondary master (like Secondary NN) would not affect this task, but another standby master would

{noformat}
        if (execwrappers.size() > 0) {
          results.addAll(execwrappers);
{noformat}
- Change to !isEmpty() to appease the anti-size() gods?

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