stackabletech / stackabletech/tokio-zookeeper
Connect Method without default watcher
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 78
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to use tokio_zookeeper to connect to a clickhouse-keeper instance (outside the scope of this project I know)
Clickhouse keeper does not support these features
- addWatch doesn't work with PERSISTENT watches
- removeWatch and removeAllWatches aren't supported
- setWatches isn't supported
Which is why I assume I am getting errors when trying to connect
Error { source: None, message: "failed to enqueue new request: Canceled" }
I realize that the default watcher is to keep consistency with the Java client implementation but would it be possible (acceptable?) to figure out a connection without the watcher?
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 tokio_zookeeper's connection setup and its default watcher behavior, but no file or test is identified. Review how watcher-related requests are issued during connection and compare them with ClickHouse Keeper's unsupported features; done means a connection can be established without the default watcher, with coverage for the reported Canceled error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100