hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2670) Reader atomicity broken in trunk and branch
Date Fri, 11 Jun 2010 21:34:15 GMT

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

ryan rawson commented on HBASE-2670:

ICVs dont take part in this new concurrency system.  They are not actually being 'updated
in place' but KeyValues are being 'overwritten'.  Given there is only 1 row/column involved
in an ICV, there is no multi-KeyValue coherency to worry about here.   ICVs use memstoreTS==0
even (and are always included in every scan).

In the future I think it might be possible to insert a new KV then delete the old one out
of memstore... that shouldn't cause any issues with scanners, but we can do that later.

> Reader atomicity broken in trunk and branch
> -------------------------------------------
>                 Key: HBASE-2670
>                 URL: https://issues.apache.org/jira/browse/HBASE-2670
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.20.5, 0.21.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>         Attachments: hbase-2670.txt
> There appears to be a bug in HBASE-2248 as committed to trunk. See following failing
> 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.

View raw message