offset are null and current lag is 0
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Hi,
I have a 0.10.2.1 kafka cluster and built from head today and there are some consumer_groups that always report null for all of their partitions:
```
"current-lag": 0,
"owner": "/10.1.17.218",
"offsets": [
null,
null,
null,
null,
null,
null,
null,
null,
null,
```
In Kafka Manager the log size is 0 and the consumer offset is either 0 or -1. Screenshot below. What am I supposed to be doing here? Why is Burrow sending emails? My threshold is set to '3', is my only recourse to blacklist this consumer group for now?
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
No source file or test is named. Reproduce the null offsets and zero current lag with the reported Kafka 0.10.2.1 cluster, then trace the consumer-group offset handling. Done means the alert behavior is explained and corrected or the expected handling is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100