[
https://issues.apache.org/jira/browse/AMBARI-12489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636327#comment-14636327
]
Hudson commented on AMBARI-12489:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3146 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3146/])
AMBARI-12489. Ambari server deadlock while deploying using blueprints. (swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=558f64d164f02e0148e47e3d1714eb430466f437)
*
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.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)
