You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/12/20 16:53:00 UTC
[jira] [Commented] (ZOOKEEPER-3125) Pzxid inconsistent issue when
replaying a txn for a deleted node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726031#comment-16726031 ]
Hudson commented on ZOOKEEPER-3125:
-----------------------------------
SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #317 (See [https://builds.apache.org/job/ZooKeeper-trunk/317/])
ZOOKEEPER-3125: Only patching the pzxid when it's larger than the (fangmin: rev db53d02869faa7c9819689315daa3933125c89a8)
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/DataTree.java
* (edit) zookeeper-server/src/test/java/org/apache/zookeeper/server/DataTreeTest.java
> Pzxid inconsistent issue when replaying a txn for a deleted node
> ----------------------------------------------------------------
>
> Key: ZOOKEEPER-3125
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3125
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Reporter: Fangmin Lv
> Assignee: Fangmin Lv
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 3.6.0, 3.5.5
>
> Time Spent: 9.5h
> Remaining Estimate: 0h
>
> When taking snapshot or syncing snapshot from leader, it's having fuzzy snapshot, which means the parent node might already serialized before the child get deleted, during replay the txn it will skip update the parent pzxid in this case, which will cause inconsistency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)