Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 8 Dec 2016 01:23:59 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13021138.1479303290000.467767.1481160239684@Atlassian.JIRA>
In-Reply-To: <JIRA.13021138.1479303290000@Atlassian.JIRA>
References: <JIRA.13021138.1479303290000@Atlassian.JIRA> <JIRA.13021138.1479303290893@arcas>
Subject: [jira] [Updated] (AMBARI-18906) Remove Unnecessary Locks Inside Of
 Config Business Object Implementations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 08 Dec 2016 01:24:01 -0000


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

Jonathan Hurley updated AMBARI-18906:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Remove Unnecessary Locks Inside Of Config Business Object Implementations
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-18906
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18906
>             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
>
>         Attachments: AMBARI-18906.patch
>
>
> {{ConfigImpl}} uses internal locks around state which can lead to deadlocks when this in called in the context of other business objects. In most cases, this state-full data does not need locks placed around it. 
> {{ConfigImpl}} should be changed to:
> - No longer store entity information
> - No longer require locks around primitive state


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