hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16801) The Append/Increment may return the data from future
Date Tue, 11 Oct 2016 22:12:20 GMT

     [ https://issues.apache.org/jira/browse/HBASE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-16801:
--------------------------
    Priority: Critical  (was: Minor)

I marked this critical. I see misreading if read wrong mvcc.  In fact, should the mvcc be
volatile since it could be set by one thread but read by another setting up a Scanner?

> The Append/Increment may return the data from future
> ----------------------------------------------------
>
>                 Key: HBASE-16801
>                 URL: https://issues.apache.org/jira/browse/HBASE-16801
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: ChiaPing Tsai
>            Assignee: ChiaPing Tsai
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16801.v0.patch
>
>
> OperationContext maintains the mvcc as a static member, so any Append’s and Increment’s
read point will be changed by others. That is, a retrying Append/Increment may “see” the
future data.
> This is a master only issue.



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

Mime
View raw message