[CURATOR-319] NodeCache recreates deleted parents of the node being cached
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Starting with Curator 2.10.0, the NodeCache will spontaneously re-create parents of the node being cached if one of them is deleted. As an example, if there is a NodeCache watching node /a/b/c and node b is deleted, the cache will immediately recreate node b (but not c) when the change is processed. This seems to stem from this commit: https://github.com/apache/curator/commit/f02fb225d531506444b54cdf5effb0529a35cdb0
This was not the behavior prior to 2.10.0, and seems pretty unexpected.
---
Originally reported by twbecker, imported from: NodeCache recreates deleted parents of the node being cached
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.