hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4139) Potential ResourceManager deadlock when SchedulerEventDispatcher is stopped
Date Fri, 13 Apr 2012 13:53:17 GMT

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

Jason Lowe updated MAPREDUCE-4139:

    Attachment: MAPREDUCE-4139.patch

Updated patch to fix for findbug warning.

Test failures are unrelated to this patch.  They are the same failures that were recently
reported for MAPREDUCE-4144 and others.
> 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
>         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


View raw message