[
https://issues.apache.org/jira/browse/MAPREDUCE-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rushabh S Shah updated MAPREDUCE-4775:
--------------------------------------
Target Version/s: 3.0.0 (was: 3.0.0, 0.23.11)
Talked to [~revans2] offline and removing 0.23.11 from target version.
> Reducer will "never" commit suicide
> -----------------------------------
>
> Key: MAPREDUCE-4775
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4775
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> In 1.0 there are a number of conditions that will cause a reducer to commit
> suicide and exit.
> This includes if it is stalled, if the error percentage of total fetches is
> too high. In the new code it will only commit suicide when the total number
> of failures for a single task attempt is >= max(30, totalMaps/10). In the
> best case with the quadratic back-off to get a single map attempt to reach 30
> failure it would take 20.5 hours. And unless there is only one reducer
> running the map task would have been restarted before then.
> We should go back to include the same reducer suicide checks that are in 1.0
--
This message was sent by Atlassian JIRA
(v6.2#6252)
