hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingcheng Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16578) Mob data loss after mob compaction and normal compcation
Date Mon, 12 Sep 2016 07:20:20 GMT

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

Jingcheng Du commented on HBASE-16578:

Thanks [~huaxiang]. Good finding!
The scanners in MOB rely on the maxSeqId in StoreFiles.
I debug this issue, and find that the maxSeqId is not loaded by {{StoreFile}} in {{StoreFileScanner.getScannersForStoreFiles()}}
in {{Compactor.compact()}}.
Would you like to give a patch to fix this? Override this compact method in {{DefaultMobCompactor}}
or create readers of the StoreFile before they are sorted in {{StoreFileScanner.getScannersForStoreFiles()}}?

> Mob data loss after mob compaction and normal compcation
> --------------------------------------------------------
>                 Key: HBASE-16578
>                 URL: https://issues.apache.org/jira/browse/HBASE-16578
>             Project: HBase
>          Issue Type: Bug
>          Components: mob
>    Affects Versions: 2.0.0
>            Reporter: huaxiang sun
>            Assignee: huaxiang sun
>         Attachments: TestMobCompaction.java, TestMobCompaction.java
> I have a unittest case, which could explore the mob data loss issue. The root cause is
that with the following line:
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/mob/compactions/PartitionedMobCompactor.java#L625
> It will make the old mob reference cell win during compaction.

This message was sent by Atlassian JIRA

View raw message