[
https://issues.apache.org/jira/browse/HBASE-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405612#comment-13405612
]
Anoop Sam John commented on HBASE-6311:
---------------------------------------
Store#compactStore(final Collection<StoreFile> filesToCompact,
final boolean majorCompaction, final long maxId)
{code}
// Find the smallest read point across all the Scanners.
long smallestReadPoint = region.getSmallestReadPoint();
MultiVersionConsistencyControl.setThreadReadPoint(smallestReadPoint);
{code}
This setting the read point is the issue? With removal of this line I am able
to pass ur test case. smallestReadPoint ideally should be used for resetting
the memstoreTs. [Any other usages?]
Obviously it should not be used for deciding what to scan. Compact need to scan
every thing from the files.
> 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 SmallestReadPoin.
> 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
