linkedin / linkedin/Burrow

Memory leak problem

Open
#580 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

I'm using master code build with go 1.13.4,I hava configed 4 kafka cluster,but the memory become larger when burrow started a few hours later. The server total memory 16GB. Nov 05 and Nov 06 I restart burrow.
![image](https://user-images.githubusercontent.com/8575470/68539954-fad62400-03c5-11ea-9cce-e9b369c46af6.png)
The storage set below.
```
[storage.default]
class-name="inmemory"
workers=20
intervals=30
expire-group=600
min-distance=1
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported growth using the provided four-cluster setup and the [storage.default] configuration. Monitor Burrow's memory over several hours and compare behavior across storage settings; done means identifying a reproducible cause and confirming that memory remains stable after the fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
backend, stream-processing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.