hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (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 20:28:36 GMT

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

Lars Hofhansl commented on HBASE-9485:
--------------------------------------

We can add this to 0.94 as well, no?
If it is built against Hadoop 2.x it should just work.

> 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.96.2
>
>         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