[
https://issues.apache.org/jira/browse/HBASE-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564631#comment-15564631
]
Hudson commented on HBASE-16801:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1765 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/1765/])
HBASE-16801 The Append/Increment may return the data from future (tedyu: rev
0f21c41eda828eae42dd9bab102988c252b1088a)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestServerNonceManager.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ServerNonceManager.java
> 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: Minor
> 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)
