ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-12924) Upgrade Orchestration To Skip Unhealthy Hosts
Date Mon, 31 Aug 2015 17:30:46 GMT


Hudson commented on AMBARI-12924:

SUCCESS: Integrated in Ambari-branch-2.1 #448 (See [])
AMBARI-12924 - Upgrade Orchestration To Skip Unhealthy Hosts (jonathanhurley) (jhurley:
* ambari-server/src/main/java/org/apache/ambari/server/stack/
* ambari-server/src/test/java/org/apache/ambari/server/state/
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/
* ambari-server/src/main/java/org/apache/ambari/server/stack/

> Upgrade Orchestration To Skip Unhealthy Hosts
> ---------------------------------------------
>                 Key: AMBARI-12924
>                 URL:
>             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

View raw message