galrose opened a new issue #10136:
URL: https://github.com/apache/pulsar/issues/10136
**Describe the bug**
I'm producing to a persistent topic in pulsar with no subscriptions.
While producing the direct memory increases every time there is disk latency
from the bookie's storage.
I've stopped writing and the memory (in broker ) doesn't get released. It's
been that way for a few days and I haven't found a solution.
**To Reproduce**
Steps to reproduce the behavior:
1. Create pulsar cluster from the ansible play book (Either 2.7.0 or 2.7.1 I
tried on both)
2. Create a persistent topic (QW == QA == 3)
3. Produce to the topic using pulsar perf
4. Wait for deletions or other actions that heavily affect the storage.
5. Stop producing and the direct memory doesn't get released.
**Expected behavior**
I expect the broker to release the memory.
I don't understand why it increased every time there was throttling from the
bookie in the first place and even if so, it should go back down when it
successfully writes to all the bookies.
**Desktop (please complete the following information):**
- OS: Centos 7.8
**Additional context**
I've been struggling with this for a while and were trying to use pulsar as
a central messaging platform for a large organization with multiple tenants. It
would really help if there is a solution to this problem either in the
configuration or if it's a bug then someone that understands could look at it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
