ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Slacum (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11744) Ambari Server deadlocks when adding service / adding host
Date Sat, 15 Aug 2015 14:40:45 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-11744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698290#comment-14698290
] 

William Slacum commented on AMBARI-11744:
-----------------------------------------

I just ran into this w/ Ambari 1.7. Looking over the patch, it looks like there's still potential
for deadlock within {{ConfigGroupImpl#delete}}. It attempts to grab two write locks in a row
and I don't see any protections against deadlock there (ie, no timeouts).

> Ambari Server deadlocks when adding service / adding host
> ---------------------------------------------------------
>
>                 Key: AMBARI-11744
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11744
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.1
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>             Fix For: 2.1.0, 2.0.2
>
>         Attachments: jstack-20150518.txt
>
>
> This was observed while adding Ganglia to an existing cluster via Add Services Wizard.
> It hung after clicking Deploy at task 2 / 6.
> Browser tools showed that it was doing a PUT and this call timed out after 3 mins.
> All subsequent API calls hung. Ambari Server was not responsive at all to any API calls
after that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message