Burrow reports Kafka lag from a topic that a consumer stopped subscribing.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
We lately had to update one of our consumers to stop subscribing events from a specific topic. Since then, Burrow has started reporting that the consumer has Kafka lag due to the topic stopped subscribing from. Is there a way to resolve this issue? Thanks.
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
Start by tracing Burrow's Kafka consumer-lag handling for topics no longer in a consumer's subscription. Reproduce the report with a consumer that unsubscribes from one topic, then determine the expected treatment of that topic and add a regression check; done means intentionally unsubscribed topics are handled correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100