hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17112) Prevent setting timestamp of delta operations the same as previous value's
Date Sat, 04 Feb 2017 12:36:51 GMT

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

Hudson commented on HBASE-17112:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #92 (See [https://builds.apache.org/job/HBase-1.3-JDK7/92/])
HBASE-17112 Prevent setting timestamp of delta operations being same as (yangzhe1991: rev
2320b1c04dce9235323895e9810d3010a0322e8f)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java


> Prevent setting timestamp of delta operations the same as previous value's
> --------------------------------------------------------------------------
>
>                 Key: HBASE-17112
>                 URL: https://issues.apache.org/jira/browse/HBASE-17112
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.1.7, 0.98.23, 1.2.4
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 2.0.0, 1.4.0, 1.3.1, 1.2.5, 0.98.24, 1.1.8
>
>         Attachments: HBASE-17112-branch-1.1-v1.patch, HBASE-17112-branch-1.1-v1.patch,
HBASE-17112-branch-1-v1.patch, HBASE-17112-branch-1-v1.patch, HBASE-17112-v1.patch, HBASE-17112-v2.patch,
HBASE-17112-v2.patch
>
>
> In delta operations, Increment and Append. We will read current value first and then
write the new whole result into WAL as the type of Put with current timestamp. If the previous
ts is larger than current ts, we will use the previous ts.
> If we have two Puts with same TS, we will ignore the Put with lower sequence id. It is
not friendly with versioning. And for replication we will drop sequence id  while writing
to peer cluster so in the slave we don't know what the order they are being written. If the
pushing is disordered, the result will be wrong.
> We can set the new ts to previous+1 if the previous is not less than now.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message