hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allan Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17482) mvcc mechanism fails when using mvccPreAssign
Date Sun, 22 Jan 2017 01:03:26 GMT

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

Allan Yang commented on HBASE-17482:

[~stack], we are porting mvccPreAssign to our costom 1.1.2 branch, when I doing this, I have
to look very carefully, to make sure all the cells in the memstore are stamped with mvcc.
After I have done that, when I looked back at the master branch's code, I notice there is
no guarantee there, then I wrote a UT which conformed my thought.

> mvcc mechanism fails when using mvccPreAssign
> ---------------------------------------------
>                 Key: HBASE-17482
>                 URL: https://issues.apache.org/jira/browse/HBASE-17482
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0..
>            Reporter: Allan Yang
>            Assignee: Allan Yang
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: HBASE-17482.patch, HBASE-17482.v2.patch, HBASE-17482.v3.patch
> If mvccPreAssign and ASYNC_WAL is used, then cells may have been commited to memstore
before append thread can stamp seqid to them. The unit test shows everything.

This message was sent by Atlassian JIRA

View raw message