hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13531) After 4/18/15 merge, flakey failures of TestAcidGuarantees#testMobScanAtomicity
Date Thu, 14 May 2015 13:30:00 GMT

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

Anoop Sam John commented on HBASE-13531:
----------------------------------------

Ya we can apply the readPnt check on MOB file reader also.
But one doubt
We will read cells from MOB files only on demand right. First we read from ref cf files and
there any way the readPoint check is there. Only if it passes, we will call get cell on MOB.

Or the case is like with same key (rk,cf,q,ts,type) we have 2 cells and old cell in ref cf
got cleared by readPoint check but we read the new cell from MOB file?

> After 4/18/15 merge, flakey failures of TestAcidGuarantees#testMobScanAtomicity
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-13531
>                 URL: https://issues.apache.org/jira/browse/HBASE-13531
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver, Scanners
>    Affects Versions: hbase-11339
>            Reporter: Jonathan Hsieh
>             Fix For: hbase-11339
>
>         Attachments: HBASE-13531.diff
>
>
> After the merge of master from 4/18/15 with hbase-11339 branch, we encounter some atomicity
violations.  We want to fix before calling merge to trunk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message