hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingcheng Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13531) After 4/18/15 merge, flakey failures of TestAcidGuarantees#testMobScanAtomicity
Date Sat, 02 May 2015 04:48:06 GMT

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

Jingcheng Du commented on HBASE-13531:
--------------------------------------

Hi Jon, in the flushing, the mob file and store file are written at the same time, and the
the commit sequence is firstly mob file, and store file after that. After the store file is
committed, both mob file and store file are visible.
So I think this doesn't bring violation.
Speaking of race between CF, I raise the assumption, the memstore is a set which can guarantee
there are not rows with the same key in the memstore at the same, I think that can break the
violation, but not only for mob, but for all. Is that possible.


> 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
>
>
> 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