[
https://issues.apache.org/jira/browse/AMBARI-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15040108#comment-15040108
]
Hadoop QA commented on AMBARI-14188:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12775595/AMBARI-14188.v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4475//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4475//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: Ambari-2.1.3
>
> Attachments: 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)
