Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 4 Dec 2013 01:12:35 +0000 (UTC)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12667723.1378780388961.66945.1386119555666@arcas>
In-Reply-To: <JIRA.12667723.1378780388961@arcas>
References: <JIRA.12667723.1378780388961@arcas>
Subject: [jira] [Commented] (HBASE-9485) TableOutputCommitter should
 implement recovery if we don't want jobs to start from 0 on RM restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Devaraj Das commented on HBASE-9485:
------------------------------------

+1 from me as well. Thanks [~vinodkv] for the explanation.

> TableOutputCommitter should implement recovery if we don't want jobs to start from 0 on RM restart
> --------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-9485
>                 URL: https://issues.apache.org/jira/browse/HBASE-9485
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 9485-v2.txt
>
>
> HBase extends OutputCommitter which turns recovery off. Meaning all completed maps are lost on RM restart and job starts from scratch. FileOutputCommitter implements recovery so we should look at that to see what is potentially needed for recovery.


--
This message was sent by Atlassian JIRA
(v6.1#6144)