You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2023/02/28 12:52:51 UTC

[GitHub] [pulsar] sourabhaggrawal edited a discussion: Bookkeeper Direct Memory Consumption is High

GitHub user sourabhaggrawal edited a discussion: Bookkeeper Direct Memory Consumption is High

We have observed that in bookkeeper Direct Memory which was set to 4GB for a long time (2-3 years), is getting consumed fully (may be after upgrading to 2.10.1) , we noticed this 3 months back thats when we upgraded the cluster to 2.10.1.

We went ahead and beefed up the server with double capacity and allocated 20GB of Direct Memory (because thats where it got stabilised). But now we see that even 20GB was also getting fully consumed and bookkeeper kept restarting 


We also have a problem of our ledger disk getting full and not deleting the expired ledgers or not reclaiming the free space and I believe Direct Memory could be a reason of this problem too. Because GC also make use of Memory to delete ledgers. 

I have attached a screenshot of DirectMemory of one node and the pattern is same for other nodes too.

Any leads on what could be the reason and how to fix it ?

<img width="1335" alt="Screenshot 2023-02-28 at 6 19 34 PM" src="https://user-images.githubusercontent.com/70515711/221858733-016cd226-d73e-4ef6-af69-614c6f6f75b7.png">


GitHub link: https://github.com/apache/pulsar/discussions/19663

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org