You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2016/10/03 17:48:20 UTC
[jira] [Resolved] (AMBARI-18475) Remove Global Cluster Lock Shared
Between Business Objects
[ https://issues.apache.org/jira/browse/AMBARI-18475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley resolved AMBARI-18475.
--------------------------------------
Resolution: Fixed
> 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)