-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broker OOM and memory leak, possibly due to ledger loss #12716
Comments
@yonyong @hangc0276 Please help check the issue. |
And finally after correctly turning on the leak detection, So we can see where the leak comes from. The leak log is quite long, click details to reveal it.
Not mean to pollute this thread but this may be related to #11396 |
I will check this issue. |
@YanshuoH Thanks for you report. Would you please paste your configuration for broker and bookkeeper? |
Sure. A bit strange (annoying) thing is that I've enabled lead detection up to paranoid, but didn't find any leak report. Broker Conf
Bookie Conf
|
Ok, I will take a look. |
In pulsar v2.8.1, broker oom also appears. |
Is there any progress on this bug? I also encountered broker oom in pulsar v2.8.1. |
After upgraded to v2.8.2, the OOM issue disappears. |
Hi,
Describe the bug
Recently encountered a memory leak in Pulsar Broker. I've tried to identify the issue with logs like below.
I've enabled
io.netty.leakDetectionLevel
up toparanoid
andio.netty.leakDetection.targetRecords=40
, didn't find any leak messages appear.We have 4 pulsar clusters:
The only difference of the cluster in question is that I've enabled Geo-Replication on all namespaces. So I disable it, but the memory leak remains.
Screenshots
It is only a testing cluster with not much memory configured. But I believe the screenshots can show the leak.
Additional context
I might take a wild guess that the memory leak may come from Bookie side data loss.
I've found some error logs in it:
This is because we've encountered some Kubernetes Node issue long times ago and some of the ledgers are unintentionally deleted.
And I can confirm that all the bookies are working just fine without any memory leak issue (except the above exceptions)
Tell me if there's any clue or anything I can do to diagnostic the memory leak.
Thanks.
The text was updated successfully, but these errors were encountered: