You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Nemon Lou (JIRA)" <ji...@apache.org> on 2013/08/28 15:08:52 UTC

[jira] [Created] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommiter API

Nemon Lou created MAPREDUCE-5485:
------------------------------------

             Summary: Allow repeating job commit by extending OutputCommiter API
                 Key: MAPREDUCE-5485
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5485
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
    Affects Versions: 2.1.0-beta
            Reporter: Nemon Lou


There are chances MRAppMaster crush during job committing,or NodeManager restart cause the committing AM exit due to container expire.In these cases ,the job will fail.
However,some jobs can redo commit so failing the job becomes unnecessary.
Let clients tell AM to allow redo commit or not is a better choice.
This idea comes from Jason Lowe's comments in MAPREDUCE-4819 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira