[
https://issues.apache.org/jira/browse/HBASE-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839304#comment-13839304
]
Hudson commented on HBASE-9485:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #863 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/863/])
HBASE-9485 TableOutputCommitter should implement recovery if we don't want jobs
to start from 0 on RM restart (tedyu: rev 1547803)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableOutputCommitter.java
> 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)
