[
https://issues.apache.org/jira/browse/AMBARI-20692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367080#comment-16367080
]
Hudson commented on AMBARI-20692:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-20692. Add Ability to Pause An Upgrade In Progress (aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=532ab597b439be54cde5de21ea35340dee0e3587])
* (edit) ambari-web/app/routes/stack_upgrade_routes.js
* (edit)
ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs
* (edit) ambari-web/test/views/main/service/menu_test.js
* (edit) ambari-web/test/views/main/service/service_test.js
> Add Ability to Pause An Upgrade In Progress
> -------------------------------------------
>
> Key: AMBARI-20692
> URL: https://issues.apache.org/jira/browse/AMBARI-20692
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Major
> Fix For: 2.5.1
>
> Attachments: AMBARI-20692.patch
>
>
> During an upgrade, there is no ability to arbitrarily pause the request and
> gain control of the cluster back. If there is a pre-defined manual task or a
> failure which cannot be skipped, then the user has the ability to pause the
> upgrade (which in turn aborts the request temporarily).
> There should be a way to do this during the upgrade while it's running a
> command. The following are some example of ways in which this would be useful:
> - During a long running rolling upgrade, the customer may need to regain
> control of Ambari to restart a component. They cannot necessarily wait for
> the upgrade to finish or wait for a spot where the UI presents them the
> option to pause.
> - If an upgrade is having difficulty due to a configuration property in
> {{ambari.properties}}, the administrator will want to pause the upgrade in
> order to shut down Ambari and make the configuration changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
