You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2012/07/05 21:47:34 UTC

[jira] [Updated] (MAPREDUCE-4359) Potential deadlock in Counters

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

Tom White updated MAPREDUCE-4359:
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I just committed this. (I ran unit tests and test-patch and both looked OK.)
                
> Potential deadlock in Counters
> ------------------------------
>
>                 Key: MAPREDUCE-4359
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4359
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 1.0.3
>            Reporter: Todd Lipcon
>            Assignee: Tom White
>             Fix For: 1.2.0
>
>         Attachments: 1_jcarder_result_0.dot.png, MAPREDUCE-4359.patch
>
>
> jcarder identified this deadlock in branch-1 (though it may also be present in trunk):
> - Counters.size() is synchronized and locks Counters before Group
> - Counters.Group.getCounterForName() is synchronized and calls through to Counters.size()
> This creates a potential cycle which could cause a deadlock (though probably quite rare in practice)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira