You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2011/05/17 18:35:47 UTC
[jira] [Created] (MAPREDUCE-2504) MR 279: race in
JobHistoryEventHandler stop
MR 279: race in JobHistoryEventHandler stop
--------------------------------------------
Key: MAPREDUCE-2504
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2504
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Reporter: Siddharth Seth
Assignee: Siddharth Seth
Fix For: 0.23.0
The condition to stop the eventHandling thread currently requires it to be 'stopped' AND interrupted. If an interrupt arrives after a take, but before handleEvent is called - the interrupt status ends up being handled by hadoop.util.Shell.runCommand() - which ignores it (and in the process resets the flag).
The eventHandling thread subsequently hangs on eventQueue.take()
This currently randomly fails unit tests - and can hang MR AMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-2504) MR 279: race in
JobHistoryEventHandler stop
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar resolved MAPREDUCE-2504.
--------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
I just committed this to MR-279. thanks sid!
> MR 279: race in JobHistoryEventHandler stop
> --------------------------------------------
>
> Key: MAPREDUCE-2504
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2504
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 0.23.0
>
> Attachments: MR2504.patch, MR2504_2.patch, MR2504_3.patch
>
>
> The condition to stop the eventHandling thread currently requires it to be 'stopped' AND interrupted. If an interrupt arrives after a take, but before handleEvent is called - the interrupt status ends up being handled by hadoop.util.Shell.runCommand() - which ignores it (and in the process resets the flag).
> The eventHandling thread subsequently hangs on eventQueue.take()
> This currently randomly fails unit tests - and can hang MR AMs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira