influxdata / influxdata/rskafka
Metadata from controller
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 342
- Forks
- 45
- Avg merge
- 4h 45m
- Merged PRs (30d)
- 3
Description
For certain read actions like getting the partition leader or getting a topic list we currently use an arbitrary broker. This is technically allowed and will eventually lead to the correct results (at least as far as my understanding goes). However this creates some delays, esp. when acting on a topic that was just created by the controller and our arbitrary broker is not the same.
We might instead use the controller connection in more places to reduce this delay.
Contributor guide
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
Start by tracing the read actions for partition-leader and topic-list requests that currently use an arbitrary broker, then inspect how the controller connection is available. Define the affected requests and verify that they use the controller without changing results; done means the relevant reads avoid the delay caused by a newly created topic being unknown to the selected broker.
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
- Needs clarification
- Newbie friendliness
- 35/100