Bug: Fail fast on UNKNOWN_MEMBER_ID instead of retrying.
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 504
- Forks
- 263
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 5
Description
We shouldn't retry on UNKNOWN_MEMBER_ID on consume from Kafka. It is a non-retriable protocol error
If the broker doesn't know the member.id, it means the member has been removed from the group (timeout/rebalance). The broker will never accept this stale ID again. Retrying just creates an infinite loop.
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 Kafka consume path that handles broker protocol errors, focusing on UNKNOWN_MEMBER_ID. Confirm how retries are triggered and identify the relevant tests or test entry point while reading that path. Done means UNKNOWN_MEMBER_ID fails fast instead of being retried indefinitely after a member is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100