hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chunhui shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6311) Data error after compaction because of scanners
Date Tue, 03 Jul 2012 05:15:02 GMT

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

chunhui shen commented on HBASE-6311:

bq.But I don't know why we add the the condition( kv.getMemstoreTS() <= maxReadPointToTrackVersions)
in the ScanQueryMatcher

I'm clear about this, because we should keep old scanner see the KV even if it is already
been deleted.

So I think we could fix this issue as the following:

if(kv.getMemstoreTS() > maxReadPointToTrackVersions)
return MatchCode.INCLUDE;

> Data error after compaction because of scanners
> -----------------------------------------------
>                 Key: HBASE-6311
>                 URL: https://issues.apache.org/jira/browse/HBASE-6311
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.94.0
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>            Priority: Blocker
>         Attachments: HBASE-6311-test.patch
> It is a big problem:
> When we do compaction, we will use region.getSmallestReadPoint();
> It will make data mistake after compaction because we will skip some data bigger than
> I upload the test case for this issue first.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message