zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-3127) Fixing potential data inconsistency due to update last processed zxid with partial multi-op txn
Date Thu, 23 Aug 2018 06:51:00 GMT

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

ASF GitHub Bot updated ZOOKEEPER-3127:
--------------------------------------
    Labels: pull-request-available  (was: )

> 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
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 3.6.0, 3.5.5, 3.4.14
>
>
> 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)

Mime
View raw message