[ZOOKEEPER-4874] Avoid using fuzzy snapshots.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: luoxin
• Created: 12/Oct/24 02:34
• Updated: 15/Oct/24 03:27

Description

Currently, ZooKeeper uses a fuzzy snapshot method that allows write requests to continue processing while taking a snapshot. However, this approach does not retain an instantaneous data view during the serialization snapshot, leading to some issues( ZOOKEEPER-4846, ZOOKEEPER-3145). There is a need to optimize this process in order to maintain a consistent and accurate data view., 

We can optimize the snapshot process by caching the change and applying it after the snapshot is finished to avoid a fuzzy snapshot.

 

Issue Links

• relates to: ZOOKEEPER-4306 CloseSessionTxn contains too many ephemal nodes cause cluster crash
• relates to: ZOOKEEPER-4846 Failure to reload database due to missing ACL
• relates to: ZOOKEEPER-3145 Potential watch missing issue due to stale pzxid when replaying CloseSession txn with fuzzy snapshot