openstack
/
large-scale
Code Issues Proposed changes

Add information about nova setting update_resources_interval 

At large scale, we noticed that nova-compute was sending a lot of
messages to conductor.
Tuning the update_resources_interval parameter helped us drastically
reducing the load on rabbit and nova side.

Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
Change-Id: Id4405691dcd4051ec64a448a82896c4f3e2a9594
This commit is contained in:
Arnaud Morin 2023-06-15 11:41:48 +02:00
parent 9646979e7b
commit 9e54292102
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/journey/configure/rabbitmq.rst
View File

@ -278,3 +278,18 @@ So the recommendation is to drastically lower this value to get rid of transient
rabbit_transient_queues_ttl = 60
update_resources_interval
^^^^^^^^^^^^^^^^^^^^^^^^^
This is a nova settings: https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.update_resources_interval
This option specifies how often the update_available_resource periodic task should run.
The default periodic interval is 60 seconds, which could be too often for large-scale.
The recommendation is to increase this value to something that would fit your needs, like 600 secs:
.. code-block:: console
update_resources_interval = 600