Expose more rabbitmq tunables via config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack RabbitMQ Server Charm |
Fix Released
|
Medium
|
Edward Hope-Morley |
Bug Description
There are a number of useful tunables that are not currently exposed by the
charm but that would be of benefit to those running production clusters on
machines with above-standard resource quotas for which the current defaults
do not necessarily apply.
I would like to propose that we expose the following via the charm config:
* VM I/O Thread Pool (set via RABBITMQ_
The default value has increased in newer versions but in Xenial
(rabbitmq version v3.5.7) it is 30 which, according to the upstream
documentation [0], is non-optimal since the recommendation is to use
a value no lower than 96 when you have >= 8 cores (i.e. min 12 threads
per core) - which is more than likely the case for most production
environments.
* Connection backlog (set in tcp_listen_options in [2])
Again this value defaults to 128 which, for larger deployments with a
large number of clients and particularly where network interrupts are
extant and reconnects undesirable this number should be higher. Docs
suggest going up to 4096.
[0] https:/
[1] /etc/rabbitmq/
[2] /etc/rabbitmq/
Changed in charm-rabbitmq-server: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/469141
Review: https:/