Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 5 Oct 2011 06:30:36 +0000 (UTC)
From: "Sharad Agarwal (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <809931650.10638.1317796236249.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <870018719.20891.1310897699886.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2702) [MR-279] OutputCommitter
 changes for MR Application Master recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sharad Agarwal commented on MAPREDUCE-2702:
-------------------------------------------

bq. uniting isRecoverySupported and recoverTask into a single api

combining the api has problem:
- you won't know that recovery is supported or not until you use the recover task api. currently recover code path is different and only executed if recovery is supported.
- recovery is at job level, while recover task is task level. semantically it is not very clear because recover task is invoked multiple times.


> [MR-279] OutputCommitter changes for MR Application Master recovery
> -------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2702
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2702
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: mrv2
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>            Priority: Blocker
>         Attachments: MAPREDUCE-2702.patch, MAPREDUCE-2702.patch, mr2702_v1.patch, mr2702_v2.patch, mr2702_v3.patch, mr2702_v4.patch
>
>
> In MR AM recovers from a crash, it only reruns the non completed tasks. The completed tasks (along with their output, if any) needs to be recovered from the previous life. This would require some changes in OutputCommitter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira