[
https://issues.apache.org/jira/browse/AMBARI-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636325#comment-14636325
]
Hudson commented on AMBARI-12489:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.1 #250 (See
[https://builds.apache.org/job/Ambari-branch-2.1/250/])
AMBARI-12489. Ambari server deadlock while deploying using blueprints. (swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=89a7d2885467a44308e5f30b18871c324f9feae8)
*
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
> Ambari server deadlock while deploying using blueprints
> -------------------------------------------------------
>
> Key: AMBARI-12489
> URL: https://issues.apache.org/jira/browse/AMBARI-12489
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12489.patch
>
>
> Attached jstack.out with the deadlock situation. The reader threads are stuck
> on socket read while a write gets starved, this results in all subsequent
> readers waiting on the cluster global read lock to get stuck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
