hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jothi Padmanabhan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1060) JT should kill running maps when all the reducers have completed
Date Tue, 06 Oct 2009 05:11:31 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762509#action_12762509
] 

Jothi Padmanabhan commented on MAPREDUCE-1060:
----------------------------------------------

bq. When jobs finish, all running tasks should be killed via KillJobAction

Here the job did not finish, it looks like job is marked for completion only when all the
maps and reducers are finished. In this case, some maps are still running. The Job was marked
complete only when the last map finished

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message