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 "Nathan Roberts (JIRA)" <ji...@apache.org> on 2011/07/26 16:41:10 UTC
[jira] [Updated] (MAPREDUCE-1060) JT should kill running maps when
all the reducers have completed
[ https://issues.apache.org/jira/browse/MAPREDUCE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Roberts updated MAPREDUCE-1060:
--------------------------------------
Fix Version/s: 0.20.205.0
> JT should kill running maps when all the reducers have completed
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-1060
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1060
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Jothi Padmanabhan
> Assignee: Jonathan Eagles
> Fix For: 0.20.205.0
>
>
> We have seen some situations where maps are still running when all the reducers have completed. This could happen because of lost TT's, interplay of speculative tasks with bad TT's etc. If the maps take a long time to run, it unnecessarily delays the job completion time, as this map output is not required anyways. The JT should possibly kill running maps when all the reducers have completed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira