[
https://issues.apache.org/jira/browse/AMBARI-13218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906243#comment-14906243
]
Hudson commented on AMBARI-13218:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #591 (See
[https://builds.apache.org/job/Ambari-branch-2.1/591/])
AMBARI-13218 Web Client Expose Ability To Suspend and Resume Upgrade. (atkach)
(atkach:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8d9430a773107b644ac46ced61903745d9dc76e4)
* ambari-web/app/utils/db.js
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js
* ambari-web/app/messages.js
* ambari-web/app/models/upgrade_entity.js
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
* ambari-web/test/views/main/admin/stack_upgrade/upgrade_wizard_view_test.js
* ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs
* ambari-web/app/templates/application.hbs
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
* ambari-web/app/app.js
* ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* ambari-web/app/utils/helper.js
* ambari-web/test/app_test.js
> 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, AMBARI-13218_branch-2.1.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)
