[CURATOR-667] Background `getConfig` and `reconfig` could deliver abnormal path

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.6.0
• Component/s: Framework
• Assignee: Kezhu Wang
• Reporter: Kezhu Wang
• Created: 09/Apr/23 13:26
• Updated: 29/Sep/24 15:25
• Resolved: 13/Aug/23 04:24

Description

In reporting CURATOR-666, I verified that CuratorFramework::getConfig get "keeper/config" in "/zoo" and "/config" in "/zookeeper" namespace. ZOOKEEPER-4601 and ZOOKEEPER-4565 reported similar issues, we might need extra coordination with ZooKeeper community to maintain consistent between curator and zookeeper. I have bumped up an earlier discussion in both dev@curator and dev@zookeeper

Issue Links

• causes: CURATOR-710 EnsembleTracker leaking watch
• relates to: CURATOR-666 Background create strip namespace twice from path
• relates to: ZOOKEEPER-4601 Define getConfig Watcher behavior in chroot ZooKeeper
• links to: GitHub Pull Request #474