hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MAPREDUCE-4139) Potential ResourceManager deadlock when SchedulerEventDispatcher is stopped
Date Thu, 11 Oct 2012 17:50:56 GMT

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

Arun C Murthy closed MAPREDUCE-4139.
------------------------------------

    
> 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, 2.0.2-alpha
>
>         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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message