influxdata / influxdata/rskafka
`PartitionClient` may silently read from replica
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 342
- Forks
- 45
- Avg merge
- 4h 45m
- Merged PRs (30d)
- 3
Description
When a cluster re-balances, the existing partition leader may become a replica, but will not actively report that to the PartitionClient. Even worse, the read lag may trigger this Redpanda quirk even under Kafka:
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 with src/client/partition.rs lines 149-159 and trace how PartitionClient handles rebalancing and read lag. Determine how the client should recognize that a former leader is now a replica, then verify that reads cannot silently use that replica in the reported Kafka or Redpanda scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100