burrow consumergroup inconsistency
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Looking at burrow metrics there's a consumergroup on __consumer__offsets that correlates to the name i've given it in the config for consumer.local but the status is STOP with lag. When checking with kafka-consumer-groups.sh I do not see it. What is the expected functionality here? Should there be a consumer running with zero lag?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing Burrow's metrics for the configured consumer.local group with the output of kafka-consumer-groups.sh for __consumer__offsets. Trace how the STOP status and lag are derived, then document or verify the expected behavior for a configured group that is not visible to Kafka's consumer-group command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100