You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/03/02 12:55: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=15175487#comment-15175487 ] 

Hudson commented on AMBARI-15166:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.2 #448 (See [https://builds.apache.org/job/Ambari-branch-2.2/448/])
AMBARI-15166. Cluster deadlock when calling create hosts api (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1a889a4396c94b770206c540fe73b6b0ab0356be])
* ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java


> 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)