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 2015/02/23 18:33:12 UTC
[jira] [Commented] (AMBARI-9738) Ambari Server Deadlocks During
Cluster Provisioning
[ https://issues.apache.org/jira/browse/AMBARI-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333551#comment-14333551 ]
Hudson commented on AMBARI-9738:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1837 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1837/])
AMBARI-9738 - Ambari Server Deadlocks During Cluster Provisioning (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=923bf81ae125ac6581cef053aa2c31baca1dcb65)
* ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersDeadlockTest.java
* ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClustersImpl.java
> Ambari Server Deadlocks During Cluster Provisioning
> ---------------------------------------------------
>
> Key: AMBARI-9738
> URL: https://issues.apache.org/jira/browse/AMBARI-9738
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: ambariserverstack.txt
>
>
> During provisioning of a cluster, a deadlock scenario can occur between {{ClusterImpl}} and {{ClustersImpl}}.
> {noformat}
> Thread-1
> Clusters.mapHostsToCluster (writeLock)
> Cluster.refresh (writeLock)
>
> Thread-2
> Cluster.convertToResponse (readLock)
> Clusters.getHost (readLock)
>
> Thread-1 Clusters.mapHostsToCluster (writeLock)
> Thread-2 Cluster.convertToResponse (readLock)
> Thread-1 Cluster.refresh (writeLock) (BLOCKED by Thread-2)
> Thread-2 Clusters.getHost (readLock) (BLOCKED by Thread-1)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)