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 "Koji Noguchi (JIRA)" <ji...@apache.org> on 2013/04/11 21:48:13 UTC
[jira] [Resolved] (MAPREDUCE-114) All reducer tasks are finished,
while some mapper tasks are still running
[ https://issues.apache.org/jira/browse/MAPREDUCE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Noguchi resolved MAPREDUCE-114.
------------------------------------
Resolution: Won't Fix
Fixed in Yarn(MAPREDUCE-279). Not getting fixed in 0.20.*/1.*.
> All reducer tasks are finished, while some mapper tasks are still running
> -------------------------------------------------------------------------
>
> Key: MAPREDUCE-114
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-114
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Qi Liu
> Attachments: hadoop-bug-overview.png, hadoop-bug-useless-task.png
>
>
> In a high load environment (i.e. multiple jobs are queued up to be executed), when all reducer tasks of a job are finished, some mapper tasks of the same job may still running (possibly re-executed due to lost task tracker, etc).
> This should not happen when a job has at least one reducer task. When all reducer tasks are in SUCCEEDED state, the Hadoop JobTracker should kill all running mapper tasks, since execution would be meaningless. The job should also switch to SUCCEEDED state when all reducer tasks of that job succeeded successfully.
--
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