# The broker's memory has risen to the configured limit

**URL:** <https://forum.cedalo.com/t/the-brokers-memory-has-risen-to-the-configured-limit/1088>\
**Category:** Broker management and monitoring\
**Created:** [January 10, 2025, 6:37am UTC](https://forum.cedalo.com/t/the-brokers-memory-has-risen-to-the-configured-limit/1088 "2025-01-10T06:37:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Tizian](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.cedalo.com/tizian/32/33_2.png) [@Tizian](https://forum.cedalo.com/u/Tizian)\
**Post date:** [January 13, 2025, 8:21am UTC](https://forum.cedalo.com/t/the-brokers-memory-has-risen-to-the-configured-limit/1088/2 "2025-01-13T08:21:32Z")

</div>

See my response here:

> [@Retention of messages (and removal etc)](https://forum.cedalo.com/t/retention-of-messages-and-removal-etc/568/13):
>
> Hello JMH, If you are using the QoS2 level for your messaging, then the broker will keep all the messages in memory, which should be delivered to the subscriber, since it is currently not connected. This is why the memory usage will keep increasing over time. If you want to use this level of QoS it is important to know the hardware limits your broker has and adapt accordingly. In the Mosquitto Pro we have a feature, which allows to store messages not only in memory, but also in disc. This he…

---

_[View the full topic](https://forum.cedalo.com/t/the-brokers-memory-has-risen-to-the-configured-limit/1088)._