You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "mutu (Jira)" <ji...@apache.org> on 2024/12/03 03:34:00 UTC

[jira] [Commented] (ZOOKEEPER-4836) Inconsist aclIndex leads to MarshallingError

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

mutu commented on ZOOKEEPER-4836:
---------------------------------

I have add links to system logs in  ZOOKEEPER-4689.

> Inconsist aclIndex leads to MarshallingError
> --------------------------------------------
>
>                 Key: ZOOKEEPER-4836
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4836
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.10.0
>            Reporter: mutu
>            Priority: Critical
>         Attachments: node1.log, node2.log, node3.log
>
>
> There is a three-node cluster.  A client create  /1 with a new acl1 to leader.
> When leader sends the snapshot to the follower, the nic becomes fail-slow. Hence, the follower1 get aclcache(aclIndex 2) without acl1. But the follower1 get a correct datatree. When deserializing the datatree, aclIndex is reset to 1. At this time, the aclIndex is inconsistent (leader:3, follower1:1,follower2:3). The follower1 execute Txn that logs the create operation.
> In follower1, the aclIndex is set to 2 and node/1 points to 3. When executing getAcl /1, MarshallingError arises.
> System logs are attached.
> Are there any comments to figure out this issues? I will very appreciate them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)