Assess number of zookeeper watches being set by different processes types.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
Accumulo code is structured to minimize the number zookeeper connections and number of zookeeper watches. With the large number of changes made in 4.0 it is possible that these goals are not being met as well as they used to be. Developing a way to measure the number of connections and watches per process would help determine if what is happening with this goal. Would be nice to be able to see this information per server and per client. There may not be any accumulo changes needed for this, may be able to do this w/ existing zookeeper mechanisms and some scripts.
Contributor guide
Research direction
No files or tests are named. Start by reviewing existing ZooKeeper mechanisms and any scripts that can report connections and watches, then determine whether Accumulo changes are needed. Done would mean a defined way to measure these counts by process type, server, and client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100