[CURATOR-654] DistributedBarrier watcher leak
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
The DistributedBarrier adds a zookeeper exists watcher in the waitOnBarrier() method. It appears as though the watcher is never removed. In a system where DistributedBarriers are used heavily this eventually results in the system running out of memory.
---
Originally reported by sscott, imported from: DistributedBarrier watcher leak
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate DistributedBarrier and its waitOnBarrier() method, then inspect how the ZooKeeper exists watcher is registered and what lifecycle follows. Reproduce repeated barrier use and verify that completed barriers no longer cause watcher or memory growth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100