# QOS 0 Memory Exceeded

**URL:** <https://community.hivemq.com/t/qos-0-memory-exceeded/1788>\
**Category:** Uncategorized\
**Created:** [January 27, 2023, 1:20pm UTC](https://community.hivemq.com/t/qos-0-memory-exceeded/1788 "2023-01-27T13:20:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![hivemq-support](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/hivemq-support/32/357_2.png) [@hivemq-support](https://community.hivemq.com/u/hivemq-support)\
**Post date:** [January 27, 2023, 6:02pm UTC](https://community.hivemq.com/t/qos-0-memory-exceeded/1788/3 "2023-01-27T18:02:50Z")

</div>

Hi Harry,

That error generally boils down to subscribers consuming from topics slower than publishers publishing to them, creating a bottleneck. This is covered in a few places, but some documentation and discussions are below:

[https://www.hivemq.com/docs/hivemq/4.11/control-center/analytic.html#dropped-messages](https://www.hivemq.com/docs/hivemq/4.11/control-center/analytic.html#dropped-messages)

[https://community.hivemq.com/t/qos-0-memory-limit/115](https://community.hivemq.com/t/qos-0-memory-limit/115)

It may seem like a good idea at first to try to increase memory allowance when encountering this error, but in the end it is often a trap - increasing the memory used by the in memory queue without addressing the client consumption problem may only end up giving a higher ceiling before the problem reoccurs.

Thanks,  
Seth - HiveMQ Support

---

_[View the full topic](https://community.hivemq.com/t/qos-0-memory-exceeded/1788)._