You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/02/24 21:16:18 UTC
[jira] [Commented] (AMBARI-15166) Cluster deadlock when calling
create hosts api concurrently with host registration
[ https://issues.apache.org/jira/browse/AMBARI-15166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163730#comment-15163730 ]
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:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5549//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)