[
https://issues.apache.org/jira/browse/AMBARI-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250483#comment-14250483
]
Hudson commented on AMBARI-8724:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #514 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/514/])
AMBARI-8724. Rolling Upgrade - Upgrade Pack to restart standby ResourceManager
first, failover, and then upgrade the remaining RM (ncole) (ncole:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7f3b8e9f66d6eb3dba88c31c3f9561db6ea18c24)
* ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
*
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ClusterGrouping.java
*
ambari-server/src/main/java/org/apache/ambari/server/stack/MasterHostResolver.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ColocatedGrouping.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
> 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)
