Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 31 Aug 2015 17:16:46 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12860379.1440789561000.212343.1441041406327@Atlassian.JIRA>
In-Reply-To: <JIRA.12860379.1440789561000@Atlassian.JIRA>
References: <JIRA.12860379.1440789561000@Atlassian.JIRA>
 <JIRA.12860379.1440789561262@arcas>
Subject: [jira] [Commented] (AMBARI-12924) Upgrade Orchestration To Skip
 Unhealthy Hosts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on AMBARI-12924:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3354 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3354/])
AMBARI-12924 - Upgrade Orchestration To Skip Unhealthy Hosts (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=016cbb6e9f4fbcaa4a1387a9bb474086c6b0f7f8)
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
* ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* ambari-server/src/main/java/org/apache/ambari/server/stack/HostsType.java
* ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java


> Upgrade Orchestration To Skip Unhealthy Hosts
> ---------------------------------------------
>
>                 Key: AMBARI-12924
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12924
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.2.0, 2.1.2
>
>
> When creating the various stages and tasks during the initial upgrade orchestration, hosts that are unhealthy will be skipped entirely. Components and clients on these hosts will not be a part of the upgrade, regardless of whether they contain slave or client components. If, during the course up the upgrade, a host is taken out of maintenance mode, it will not be inserted into the existing orchestration.
> The upgrade packs can also define the hosts that a specific execution task can be scheduled to run on. This type of dynamic host role command creation is only done at the time an upgrade orchestration is schedule. For tasks that are schedule to run on "all" hosts, the hosts that are schedule should also not contain those which are in maintenance mode. 


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