[
https://issues.apache.org/jira/browse/HBASE-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876531#action_12876531
]
Todd Lipcon commented on HBASE-2670:
------------------------------------
Actually, I misunderstood this a little bit. The above describes the issue when
using intra-row scanning (see HBASE-2673). Without intra-row scanning, since
updateReaders is synchronized, it should only be called when the StoreScanner
is between rows.
So I think the issue may be how updateReaders itself works. It uses peak() on
the heap to find the next row it's going to, and then seeks to that one.
updateReaders, though, is called by a different thread with a different
readpoint set. So that seek pulls in values for the next row that are different
from what will be read.
I'll try to make a patch for this tomorrow.
> 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.
