Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 10 Sep 2013 02:35:51 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12667723.1378780388961.105601.1378780551573@arcas>
In-Reply-To: <JIRA.12667723.1378780388961@arcas>
References: <JIRA.12667723.1378780388961@arcas>
Subject: [jira] [Updated] (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:all-tabpanel ]

Ted Yu updated HBASE-9485:
--------------------------

    Attachment: 9485-v1.txt

Patch v1 makes TableOutputCommitter extend FileOutputCommitter
                
> 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
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 9485-v1.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 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