You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/05/11 20:44:13 UTC
[jira] [Commented] (AMBARI-16439) Restarting Upgraded Component
During a Paused Upgrade Downgrades Component To Old Version
[ https://issues.apache.org/jira/browse/AMBARI-16439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280796#comment-15280796 ]
Hudson commented on AMBARI-16439:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4824 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4824/])
AMBARI-16439 - Restarting Upgraded Component During a Paused Upgrade (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=95fb3a16cfaf542b5fe221cecaa3cbeb68528852])
* ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterEffectiveVersionTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListenerTest.java
* ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListener.java
* ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java
* ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java
> Restarting Upgraded Component During a Paused Upgrade Downgrades Component To Old Version
> -----------------------------------------------------------------------------------------
>
> Key: AMBARI-16439
> URL: https://issues.apache.org/jira/browse/AMBARI-16439
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16439.patch
>
>
> There is a regression on the 2.4.0 line when restarting components during a paused upgrade.
> STR:
> - Upgrade from HDP 2.3 to HDP 2.4, but don't finalize
> - Suspend the upgrade on the finalization step
> - Restart a ZooKeeper Server
> The commands being sent down have 2.3.x instead of 2.4.0:
> {code}
> "commandParams": {
> "service_package_folder": "common-services/ZOOKEEPER/3.4.5/package",
> "script": "scripts/zookeeper_server.py",
> "hooks_folder": "HDP/2.0.6/hooks",
> "version": "2.3.4.0-3485",
> "command_timeout": "1200",
> "script_type": "PYTHON"
> },
> "hostLevelParams": {
> "current_version": "2.3.4.0-3485",
> "custom_command": "RESTART",
> "stack_version": "2.4",
> {code}
> The problem is located in {{ClusterImpl}} in how it calculates the upgrade. In Ambari 2.2.2, it searched for upgrades, which also returned suspended upgrades. In 2.4.0, it only looks at a currently running upgrade:
> {code:title=2.4.0}
> UpgradeEntity upgradeInProgress = getUpgradeEntity();
> {code}
> {code:title=2.2.2}
> UpgradeEntity upgradeInProgress = this.getUpgradeInProgress();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)