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

Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/12/06 00:26:36 UTC

[jira] [Resolved] (HBASE-9485) TableOutputCommitter should implement recovery if we don't want jobs to start from 0 on RM restart

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

Ted Yu resolved HBASE-9485.
---------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

> 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
>             Fix For: 0.98.0, 0.94.15, 0.96.2, 0.99.0
>
>         Attachments: 9485-0.94.txt, 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)