You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Andor Molnar (JIRA)" <ji...@apache.org> on 2018/09/19 10:07:00 UTC

[jira] [Updated] (ZOOKEEPER-3127) Fixing potential data inconsistency due to update last processed zxid with partial multi-op txn

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

Andor Molnar updated ZOOKEEPER-3127:
------------------------------------
    Fix Version/s: 3.5.5

> Fixing potential data inconsistency due to update last processed zxid with partial multi-op txn
> -----------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3127
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3127
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.4, 3.6.0, 3.4.13
>            Reporter: Fangmin Lv
>            Assignee: Fangmin Lv
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 3.6.0, 3.5.5
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Found this issue while checking the code for another issue, this is a relatively rare case which we haven't seen it on prod so far.
> Currently, the lastProcessedZxid is updated when applying the first txn of multi-op, if there is a snapshot in progress, it's possible that the zxid associated with the snapshot only include partial of the multi op.
> When loading snapshot, it will only load the txns after the zxid associated with snapshot file, which could data inconsistency due to missing sub txns.
> To avoid this, we only update the lastProcessedZxid when the whole multi-op txn is applied to DataTree.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)