[
https://issues.apache.org/jira/browse/HBASE-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876526#action_12876526
]
Todd Lipcon commented on HBASE-2670:
------------------------------------
The issue is that the memstore timestamps are lost once we flush the memstore
to an HFile, and we immediately change over open scanners to scan from the
HFile in updateReaders()
I think the fix is one of the following:
- in updateReaders, scan ahead the memstore reader until the next row, and
cache those KVs internally. Then when we hit the end of the cache, do the
actual reseek in the HFile at the begining of the next row.
- in updateReaders, simply mark a flag that we need to update as soon as we hit
the next row. Then do the reseek lazily in next()
> Reader atomicity broken in trunk
> --------------------------------
>
> Key: HBASE-2670
> URL: https://issues.apache.org/jira/browse/HBASE-2670
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: ryan rawson
> Priority: Blocker
>
> There appears to be a bug in HBASE-2248 as committed to trunk. See following
> failing test:
> http://hudson.zones.apache.org/hudson/job/HBase-TRUNK/1296/testReport/junit/org.apache.hadoop.hbase/TestAcidGuarantees/testAtomicity/
> Think this is the same bug we saw early on in 2248 in the 0.20 branch, looks
> like the fix didn't make it over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
