Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 27 Sep 2016 15:42:20 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13007963.1474990939000.675025.1474990940833@Atlassian.JIRA>
In-Reply-To: <JIRA.13007963.1474990939000@Atlassian.JIRA>
References: <JIRA.13007963.1474990939000@Atlassian.JIRA> <JIRA.13007963.1474990939710@arcas>
Subject: [jira] [Created] (AMBARI-18475) Remove Global Cluster Lock Shared
 Between Business Objects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 27 Sep 2016 15:42:22 -0000

Jonathan Hurley created AMBARI-18475:
----------------------------------------

             Summary: Remove Global Cluster Lock Shared Between Business Objects
                 Key: AMBARI-18475
                 URL: https://issues.apache.org/jira/browse/AMBARI-18475
             Project: Ambari
          Issue Type: Task
          Components: ambari-server
    Affects Versions: 2.5.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 2.5.0


Remove shared instances of the shared {{ReadWriteLock}} found in {{ClusterImpl}}. For now, the lock can remain private and full encapsulated inside of {{ClusterImpl}}, but it's use and reference across the rest of Ambari should be removed.

This is part of the effort to refactor/remove the (mostly) unnecessary locks in memory. The shared instance of this lock is the number one reason that Ambari "deadlocks" when under load.


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