Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 6 Jun 2015 00:26:01 +0000 (UTC)
From: "Siddharth Wagle (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12835880.1433550255000.7989.1433550361535@Atlassian.JIRA>
In-Reply-To: <JIRA.12835880.1433550255000@Atlassian.JIRA>
References: <JIRA.12835880.1433550255000@Atlassian.JIRA>
 <JIRA.12835880.1433550255564@arcas>
Subject: [jira] [Updated] (AMBARI-11744) Ambari Server deadlocks when adding
 service / adding host
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-11744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Wagle updated AMBARI-11744:
-------------------------------------
    Attachment: jstack-20150518.txt

Jstack output with the threads waiting on read locks while withholding write locks on competing resources.

> 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
>             Fix For: 2.1.0
>
>         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)