[ 
https://issues.apache.org/jira/browse/AMBARI-15166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168028#comment-15168028
 ] 

Hadoop QA commented on AMBARI-15166:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12789604/AMBARI-15166.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  
org.apache.ambari.server.controller.internal.AlertResourceProviderTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5575//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5575//console

This message is automatically generated.

> Cluster deadlock when calling create hosts api concurrently with host 
> registration
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-15166
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15166
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.2
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15166.patch
>
>
> Deadlock was detected by JVM.
> Lock acquisition order should be changed in host registration event 
> processing.
> Currently Clusters object is called after host-local lock acquired.
> Jstack thread dump attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to