[jira] [Commented] (AMBARI-18906) Remove Unnecessary Locks Inside Of Config Business Object Implementations

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-18906:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12839387/AMBARI-18906.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9315//console

This message is automatically generated.

> 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)