[ZOOKEEPER-4601] Define getConfig Watcher behavior in chroot ZooKeeper

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: java client
• Labels: pull-request-available
• Assignee: Kezhu Wang Assign to me
• Reporter: Kezhu Wang
• Created: 26/Jul/22 13:43
• Updated: 24/Sep/23 03:45
• Resolved: 24/Sep/23 03:45

Description

After ZOOKEEPER-4565, getConfig watcher will receive path for zookeeper config node "/zookeeper/config". But if the path getConfig watcher received is somewhat sensitive to chroot path.

• With chroot path "/zookeeper", getConfig will receive path "/config".
• With other chroot paths, getConfig will receive path "/zookeeper/config".

I think we should define what path getConfig will get formally to avoid unnoticed behavior.

Issue Links

• is related to: ZOOKEEPER-838 Chroot is an attribute of ClientCnxn
• is related to: CURATOR-667 Background `getConfig` and `reconfig` could deliver abnormal path
• relates to: ZOOKEEPER-4565 Config watch path get truncated abnormally and fail chroot zookeeper client
• links to: GitHub Pull Request #1996