You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/06/03 21:59:39 UTC
[jira] [Commented] (AMBARI-11596) RU operations get aborted, must
proceed with manual upgrade
[ https://issues.apache.org/jira/browse/AMBARI-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571551#comment-14571551 ]
Hudson commented on AMBARI-11596:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2800 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2800/])
AMBARI-11596. RU operations get aborted, must proceed with manual upgrade (ncole) (ncole: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4a5076d7628acc1fdccfe3bfb90b6b687a597fe0)
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* ambari-server/src/main/java/org/apache/ambari/server/state/ConfigMergeHelper.java
* ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionManager.java
* ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionDBAccessorImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessor.java
> RU operations get aborted, must proceed with manual upgrade
> -----------------------------------------------------------
>
> Key: AMBARI-11596
> URL: https://issues.apache.org/jira/browse/AMBARI-11596
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 2.1.0
>
> Attachments: AMBARI-11596.patch
>
>
> During the middle of a Rolling Upgrade, the operations get aborted. The UI shows several as skipped, and the remainder as completed (including Finalize) even though they didn't actually run.
> Today, the way to get out of this state is to perform the RU manually (call hdp-select, restart services, call API for clients, run Finalize command, etc), which is extremely tedious, error-prone, and time-consuming.
> Provide an API that will move ABORTED requests to PENDING.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)