[
https://issues.apache.org/jira/browse/MAPREDUCE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770595#action_12770595
]
Devaraj Das commented on MAPREDUCE-1102:
----------------------------------------
The behavior of having the commitJob create a file is actually application
logic (the FileOutputCommitter in this case). So yes, there is a small window
of time when the job is considered successful, but maybe we can make that
explicit in the FileOutputCommitter contract.
On a side note, longer term, we should probably make the tasks write to a temp
JOB directory, and rename the temp job directory to the final output directory
AFTER the job is successful. That way we can avoid the special files in the
output directory of the job.
> Job gets killed even when the cleanup completes
> -----------------------------------------------
>
> Key: MAPREDUCE-1102
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1102
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.1
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Fix For: 0.22.0
>
>
> When the cleanup completes at the tasktracker and the job is killed by the
> user, the cleanup runs to completion but the job fails. Ideally if the
> cleanup is completed then the job should not be killed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
