hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9485) TableOutputCommitter should implement recovery if we don't want jobs to start from 0 on RM restart
Date Wed, 04 Dec 2013 01:02:39 GMT

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

Nick Dimiduk commented on HBASE-9485:
-------------------------------------

With [~vinodkv]'s blessing on the MR semantics, i'm +1 on the patch as posted.

> 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)

Mime
View raw message