[
https://issues.apache.org/jira/browse/MAPREDUCE-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876091#comment-16876091
]
yanglongfei edited comment on MAPREDUCE-7222 at 7/1/19 10:36 AM:
-----------------------------------------------------------------
[~anupamseth] Could you help give some advice to the problem? I found related
code is
job.scheduleTasks(job.mapTasks, job.numReduceTasks == 0);
job.scheduleTasks(job.reduceTasks, true);
was (Author: lfyangcoder):
[~anupamseth] Could you help to give some advice to the problem? I found
related code is
job.scheduleTasks(job.mapTasks, job.numReduceTasks == 0);
job.scheduleTasks(job.reduceTasks, true);
> Map tasks' outputs can not be recovered when ApplicationMaster relaunched
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-7222
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7222
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.7.3
> Reporter: yanglongfei
> Priority: Blocker
>
> When AM crashes, Yarn would launch a new AM instance and recover all its
> scheduled tasks. However mapper tasks's committed output files are not
> recovered when the number of reducers > 0. In my application which output
> files from mapper and make use of reducer to collect statistics not able to
> fully recover from the AM crash, and resulting in data from the previous
> completed mapper tasks get lost in the final output dir.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
