[
https://issues.apache.org/jira/browse/MAPREDUCE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072022#comment-13072022
]
Jonathan Eagles commented on MAPREDUCE-1060:
--------------------------------------------
test-patch results from my box.
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
(version 1.3.9) warnings.
[exec]
> 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
>
> Attachments: MAPREDUCE-1060-branch-0.20-security.patch
>
>
> 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