hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1102) Job gets killed even when the cleanup completes
Date Mon, 26 Oct 2009 16:00:59 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770071#action_12770071
] 

Owen O'Malley commented on MAPREDUCE-1102:
------------------------------------------

Rather than blocking kill-job, I think we are better off guaranteeing that if the job fails,
we will always call abortJob. Even if commitJob has started (or finished). We should also
make the FileOutputFormat abortJob delete _SUCCESS to handle this case. This would also handle
the case where the job commit task fails part way through.

I agree that all output committers may not be able to unroll their commit. However, I think
that we need to give them the ability to do the right thing.

> 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.


Mime
View raw message