stackabletech / stackabletech/tokio-zookeeper
Support pools of ZooKeeper servers (more than one addr)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 78
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
From Java docs:
To create a ZooKeeper client object, the application needs to pass a connection string containing a comma separated list of host:port pairs, each corresponding to a ZooKeeper server. The instantiated ZooKeeper client object will pick an arbitrary server from the connectString and attempt to connect to it. If establishment of the connection fails, another server in the connect string will be tried (the order is non-deterministic, as we random shuffle the list), until a connection is established. The client will continue attempts until the session is explicitly closed.
Along those lines, also handle session expiry differently from errors during reconnect.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points; start by locating the client connection and session-reconnection logic. Compare the current behavior with the linked Java documentation, then define completion as supporting comma-separated host:port endpoints with fallback and distinct session-expiry handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100