From ecff7b70566d05a62b5952d2b23909b2c1d90698 Mon Sep 17 00:00:00 2001 From: John Eckersberg Date: Mon, 22 Mar 2021 12:17:09 -0400 Subject: [PATCH] Disable RabbitMQ busy-wait for dirty cpu and dirty i/o schedulers This aligns the defaults with the recommendations from upstream: https://www.rabbitmq.com/runtime.html#busy-waiting Change-Id: Ief7fb44f53b55a73d76ef3aa29dcd17194a6fc98 --- deployment/rabbitmq/rabbitmq-container-puppet.yaml | 9 +++++---- .../notes/erl-sbwtdcpu-sbwtdio-b26506a0430480dc.yaml | 9 +++++++++ 2 files changed, 14 insertions(+), 4 deletions(-) create mode 100644 releasenotes/notes/erl-sbwtdcpu-sbwtdio-b26506a0430480dc.yaml diff --git a/deployment/rabbitmq/rabbitmq-container-puppet.yaml b/deployment/rabbitmq/rabbitmq-container-puppet.yaml index eecdb48e57..b8705fc88f 100644 --- a/deployment/rabbitmq/rabbitmq-container-puppet.yaml +++ b/deployment/rabbitmq/rabbitmq-container-puppet.yaml @@ -76,10 +76,11 @@ parameters: RabbitAdditionalErlArgs: description: Additional parameters passed to the Erlang subsystem. The string - needs to be enclosed in quotes twice. We default to +sbwt none - in order to have the erlang vm be less busy on spinlocks, but - we allow a simple way of overriding it. - default: "'+sbwt none'" + needs to be enclosed in quotes twice. We default to '+sbwt none + +sbwtdcpu none +sbwtdio none' in order to have the erlang vm be + less busy on spinlocks, but we allow a simple way of overriding + it. + default: "'+sbwt none +sbwtdcpu none +sbwtdio none'" type: string MonitoringSubscriptionRabbitmq: default: 'overcloud-rabbitmq' diff --git a/releasenotes/notes/erl-sbwtdcpu-sbwtdio-b26506a0430480dc.yaml b/releasenotes/notes/erl-sbwtdcpu-sbwtdio-b26506a0430480dc.yaml new file mode 100644 index 0000000000..43af245f87 --- /dev/null +++ b/releasenotes/notes/erl-sbwtdcpu-sbwtdio-b26506a0430480dc.yaml @@ -0,0 +1,9 @@ +--- +other: + - | + The default value of the parameter 'RabbitAdditionalErlArgs' was + updated to include the new options '+sbwtdcpu none +sbwtdio none' + which disables busy-wait for dirty cpu schedulers and dirty i/o + schedulers respectively. This aligns with the flags recommended + by RabbitMQ upstream + (https://www.rabbitmq.com/runtime.html#busy-waiting). \ No newline at end of file