Manual consumer reset and difference between end.lag and current_lag
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Hi,
I reset my kafka consumer manually (using kafka command line tools)
Now call GET /v3/kafka/(cluster)/consumer/(group)/lag to gives me a difference between partition current_lag = 0 and end.lag property = 46221:
```
{
"complete": 1,
"current_lag": 0,
"end": {
"lag": 46221,
"offset": 0,
"timestamp": 1529309335605
},
"owner": "/172.19.23.67",
"partition": 15,
"start": {
"lag": 0,
"offset": 46161,
"timestamp": 1529063264181
},
"status": "OK",
"topic": "processedJobsID"
}
```
I would like to double-confirm that this is intended.
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 at the GET /v3/kafka/(cluster)/consumer/(group)/lag endpoint and trace how current_lag, end.lag, and the start/end offsets are calculated after a Kafka command-line reset. Reproduce the reported partition state if possible, then establish whether the difference is expected and document or correct the behavior accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100