Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-4836

Inconsist aclIndex leads to MarshallingError

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Critical
    • Resolution: Unresolved
    • 3.10.0
    • None
    • server
    • None

    Description

      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.

      Attachments

        1. node3.log
          39 kB
          mutu
        2. node2.log
          40 kB
          mutu
        3. node1.log
          43 kB
          mutu

        Activity

          People

            Unassigned Unassigned
            gendong1 mutu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: