Burrow sees consumer groups, and then doesn't
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
I am running burrow 1.1.0 with kafka 0.11 and zookeeper 3.4.5. I can run a "curl http://127.0.0.1:8000/v3/kafka/local/consumer" right after I start burrow, and see all the groups. But if I run a "curl http://127.0.0.1:8000/v3/kafka/local/consumer/namehere/status" I get back
```{"error":false,"message":"consumer status returned","status":{"cluster":"local","group":"namehere","status":"NOTFOUND","complete":1,"partitions":[],"partition_count":0,"maxlag":null,"totallag":0},"request":{"url":"/v3/kafka/local/consumer/namehere/status","host":"hostname-01"}}```
Then if I run "curl http://127.0.0.1:8000/v3/kafka/local/consumer" again, I get a list without that one.
Even weirder this works fine in a staging environment, but is failing in prod. Even though both have the same versions kafka, burrow, and zookeeper.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the behavior through the mentioned /v3/kafka/local/consumer and /v3/kafka/local/consumer/namehere/status endpoints, comparing production with staging on Kafka 0.11, Burrow 1.1.0, and ZooKeeper 3.4.5. Trace why a group disappears between the list and status requests; done means the consumer list and status behavior remain consistent in both environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- api, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100