hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5485) Allow repeating job commit by extending OutputCommitter API
Date Mon, 16 Nov 2015 22:42:11 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Junping Du updated MAPREDUCE-5485:
    Attachment: MAPREDUCE-5485-v5-branch-2.7.patch

Upload a patch for branch-2.7 in case we want to commit it for 2.7.3.

> Allow repeating job commit by extending OutputCommitter 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
>            Assignee: Junping Du
>            Priority: Critical
>         Attachments: MAPREDUCE-5485-demo-2.patch, MAPREDUCE-5485-demo.patch, MAPREDUCE-5485-v1.patch,
MAPREDUCE-5485-v2.patch, MAPREDUCE-5485-v3.1.patch, MAPREDUCE-5485-v3.patch, MAPREDUCE-5485-v4.1.patch,
MAPREDUCE-5485-v4.patch, MAPREDUCE-5485-v5-branch-2.7.patch, MAPREDUCE-5485-v5.patch
> 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 was sent by Atlassian JIRA

View raw message