[
https://issues.apache.org/jira/browse/MAPREDUCE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286055#comment-13286055
]
Jason Lowe commented on MAPREDUCE-2129:
---------------------------------------
Trunk doesn't have this problem because JobImpl.getCompletedMaps() includes
failed and killed tasks as well as succeeded tasks. RMContainerAllocator uses
getCompletedMaps() to check against the slowstart threshold for launching
reducers, so it is already accounting for map tasks that may not have succeeded.
> Job may hang if mapreduce.job.committer.setup.cleanup.needed=false and
> mapreduce.map/reduce.failures.maxpercent>0
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2129
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2129
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.2, 0.20.3, 0.21.1
> Reporter: Kang Xiao
> Assignee: Subroto Sanyal
> Labels: hadoop
> Attachments: MAPREDUCE-2129.patch, MAPREDUCE-2129.patch,
> MAPREDUCE-2129.patch
>
>
> Job may hang at RUNNING state if
> mapreduce.job.committer.setup.cleanup.needed=false and
> mapreduce.map/reduce.failures.maxpercent>0. It happens when some tasks fail
> but havent reached failures.maxpercent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
