Configuration for memory watermark required
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack RabbitMQ Server Charm |
New
|
Undecided
|
Unassigned |
Bug Description
RabbitMQ by default allows itself to use up to 40% of installed RAM, based on the default setting vm_memory_
Once that watermark is hit, it attempts to free RAM by flushing messages to disk instead of RAM (while blocking clients). Various details of this are explained here: https:/
On our current deployments memory is not limited, and RabbitMQ takes this value from the full amount of host RAM - so tries to use up to 40% of 256GB/512GB/768GB. It also does not take HugePages into account, so even if 90% of RAM is permanently allocated to hugepages it does not reduce it's configuration.
The charm should expose and configure a better default watermark based on vm_memory_
description: | updated |
tags: | added: sts |