[
https://issues.apache.org/jira/browse/AMBARI-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044552#comment-15044552
]
Hudson commented on AMBARI-14188:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #3984 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3984/])
AMBARI-14188. During Upgrade Topology Manager Causes Ambari To Be (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4f0acbf1a786e07a5f76009b37b3e51cd0a6283c])
*
ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
*
ambari-server/src/test/java/org/apache/ambari/server/state/DesiredConfigTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* ambari-server/src/main/java/org/apache/ambari/server/state/DesiredConfig.java
> During Upgrade Topology Manager Causes Ambari To Be Unresponsive With
> Infinite Loop
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-14188
> URL: https://issues.apache.org/jira/browse/AMBARI-14188
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14188.v1.patch, branch-2.2-AMBARI-14188.v1.patch
>
>
> 1. Setup a small cluster with blueprints (ZK + HDFS)
> 2. Begin an upgrade (either rolling or express)
> 3. Wait for a holding phase in the upgrade
> 4. Restart Ambari
> Ambari becomes unresponsive, also high CPU usage being noticed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
