summaryrefslogtreecommitdiffstats
path: root/puppet/services/neutron-compute-plugin-nuage.yaml
diff options
context:
space:
mode:
authorMichele Baldessari <michele@acksyn.org>2016-09-20 10:11:54 +0200
committerMichele Baldessari <michele@acksyn.org>2016-09-20 10:32:44 +0200
commit859d74810baa56d7581b969743493797f2ee94d1 (patch)
treee0d575a8e6288744836234b579dea8240cd00648 /puppet/services/neutron-compute-plugin-nuage.yaml
parent5e3ad982a1ad71fb95d70c3699631bbebbb7a06e (diff)
RabbitMQ threads should be configured dynamically
Currently in puppet/services/rabbitmq.yaml we hardcode the thread pool size to 30 (via the +A30 snippet): rabbitmq_environment: RABBITMQ_SERVER_ERL_ARGS: '"+K true +A30 +P 1048576 -kernel inet_default_connect_options [{nodelay,true},{raw,6,18,<<5000:64/native>>}] -kernel inet_default_listen_options [{raw,6,18,<<5000:64/native>>}]"' Upstream rabbit has gained the ability to dynamically configure the number of threads since 3.6.2 via the following commit: https://github.com/rabbitmq/rabbitmq-server/commit/41ce5ad808863944cd6d62ce7f7e2271f1010582 Given that the default was hardcoded in rabbit from at least 3.4.0 up until 3.6.2 (see LP bug associated to this commit), we can actually remove this hardcoded value as it overrides a sane default. Before the change: /usr/lib64/erlang/erts-7.3.1/bin/beam.smp -W w -A 64 -K true -A30 -P 1048576 ... After the change: /usr/lib64/erlang/erts-7.3.1/bin/beam.smp -W w -A 64 -K true -P 1048576 ... So effectively with this change we will have the following: - With older rabbitmq versions we keep the +A30 default - With rabbitmq versions >= 3.6.2 the thread number is dynamically computed to nr_cpus * 16 Change-Id: I8d30c7d141c29fcc439d40fc767498520be7966e Closes-Bug: #1625486
Diffstat (limited to 'puppet/services/neutron-compute-plugin-nuage.yaml')
0 files changed, 0 insertions, 0 deletions