[
https://issues.apache.org/jira/browse/AMBARI-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906007#comment-14906007
]
Andrii Tkach commented on AMBARI-13218:
---------------------------------------
9389 tests complete (12 seconds)
94 tests pending
> Web Client Expose Ability To Suspend and Resume Upgrade
> -------------------------------------------------------
>
> Key: AMBARI-13218
> URL: https://issues.apache.org/jira/browse/AMBARI-13218
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13218.patch
>
>
> At the end of an upgrade, before finalization, Ambari currently prevents all
> actions on the cluster. Administrators may want to test and verify the stack
> upgrade before finalizing and committing to it, especially if there are
> unhealthy hosts which were excluded.
> There is an experimental option in the web client which enables operations.
> However, this will not work when the Ambari Server is installed on the same
> machine that hosts components, such as NameNode. The upgrade request will
> block all operations on the Ambari Server host.
> Therefore, the web client should expose the ability to shelve an upgrade. To
> the user, it appears as though the upgrade has been suspended, which can
> later be resumed. In the background, the upgrade has actually been aborted.
> When the cluster is ready to be finalized, the aborted upgrade can be placed
> back into pending to resume.
> {code:title=Abort ("Suspend") Upgrade}
> PUT api/v1/clusters/c1/upgrades/21
> {
> "Upgrade": {
> "request_status": "ABORTED"
> }
> }
> {code}
> {code:title=Resume Aborted ("Suspended") Upgrade}
> PUT api/v1/clusters/c1/upgrades/21
> {
> "Upgrade": {
> "request_status": "PENDING"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
