[
https://issues.apache.org/jira/browse/AMBARI-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044764#comment-15044764
]
Hadoop QA commented on AMBARI-14188:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12776044/branch-2.2-AMBARI-14188.v1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4509//console
This message is automatically generated.
> 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)
