Kafka Burrow Docker setup memory keeps on increasing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
I have a burrow setup done using docker. It's getting offsets for 2 clusters (2.0 and 0.8). The memory consumed by the burrow is increasing continuously. To the point that I had to setup a cron to periodically kill and restart the process. Screenshots attached.
Please let me know what all data I need to provide?
Note: It's the same case with both docker and standalone.
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 reproducing the increasing memory use in both the Docker and standalone setups while Burrow monitors the two reported Kafka clusters. Compare the behavior over time and collect the relevant runtime data requested by the issue; done means identifying a reproducible cause and confirming that memory no longer grows continuously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kafka
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100