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 "Jason Lowe (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/18 00:42:17 UTC

[jira] [Resolved] (MAPREDUCE-4139) Potential ResourceManager deadlock when SchedulerEventDispatcher is stopped

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

Jason Lowe resolved MAPREDUCE-4139.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.23.3
    
> Potential ResourceManager deadlock when SchedulerEventDispatcher is stopped
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4139
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4139
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>             Fix For: 0.23.3
>
>         Attachments: MAPREDUCE-4139.patch, MAPREDUCE-4139.patch
>
>
> When the main thread calls ResourceManager$SchedulerEventDispatcher.stop() it grabs a lock on the object, kicks the event processor thread, and then waits for the thread to exit.  However the interrupted event processor thread can end up trying to call the synchronized getConfig() method which results in deadlock.

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