Open Stack

Best Regards, Erik Olof Gunnar Andersson

From: Satish Patel <satish.txt at gmail.com>
Sent: Friday, March 20, 2020 9:23 AM
To: Grant Morley <grant at civo.com>
Cc: Erik Olof Gunnar Andersson <eandersson at blizzard.com>; openstack-discuss at lists.openstack.org
Subject: Re: Neutron RabbitMQ issues

Oh you are right here, i have following stuff in my neutron.conf on server

# Notifications
[oslo_messaging_notifications]
driver = messagingv2
topics = notifications
transport_url = rabbit://neutron:5be2a043f9a93adbd@172.28.15.192:5671<https://urldefense.com/v3/__http:/neutron:5be2a043f9a93adbd@172.28.15.192:5671__;!!Ci6f514n9QsL8ck!1JtoahRvJ7-o3UTgt10NXnicoDEJzvPdT32aMejFaeSUu2ObRSEFvEfDVSWmp4HJag$>,neutron:5be2a043f9a93adbd at 172.28.15.248:5671<https://urldefense.com/v3/__http:/neutron:5be2a043f9a93adbd@172.28.15.248:5671__;!!Ci6f514n9QsL8ck!1JtoahRvJ7-o3UTgt10NXnicoDEJzvPdT32aMejFaeSUu2ObRSEFvEfDVSXMR7XWRg$>,neutron:5be2a043f9a93adbd at 172.28.15.22:5671//neutron?ssl=1<https://urldefense.com/v3/__http:/neutron:5be2a043f9a93adbd@172.28.15.22:5671/*neutron?ssl=1__;Lw!!Ci6f514n9QsL8ck!1JtoahRvJ7-o3UTgt10NXnicoDEJzvPdT32aMejFaeSUu2ObRSEFvEfDVSUgm8NHPA$>

# Messaging
[oslo_messaging_rabbit]
rpc_conn_pool_size = 30
ssl = True


Following change i am going to made let me know if anything missing.

[DEFAULT]
executor_thread_pool_size = 2048   <--- is this correct? i didn't see anywhere "rpc_thread_pool_size"
rpc_response_timeout = 3600


[oslo_messaging_notifications]
topics = notifications
driver = noop

# Messaging
[oslo_messaging_rabbit]
rpc_conn_pool_size = 300
heartbeat_timeout_threshold = 0
ssl = True

Btw you might not necessarily be having RabbitMQ issues. You might also be experiencing something like this.
https://bugs.launchpad.net/neutron/+bug/1853071

Best Regards, Erik Andersson

Should i be adding this to all my compute nodes also ?

On Fri, Mar 20, 2020 at 11:40 AM Grant Morley <grant at civo.com<mailto:grant at civo.com>> wrote:

If you tune rabbit then for:

heartbeat_timeout_threshold = 0

That should help with the error message you are getting.

That is a lot of messages queued. We had the same because we were not using ceilometer but had the "notifications" still turned on for it for services.

Are all of the ready messages for "notifications.info<https://urldefense.com/v3/__http:/notifications.info__;!!Ci6f514n9QsL8ck!1JtoahRvJ7-o3UTgt10NXnicoDEJzvPdT32aMejFaeSUu2ObRSEFvEfDVSXCYHosug$>" for the various services ( Nova, Neutron, Keystone etc )

If that is the case you can disable those messages in your config files for those services. Look for:

# Notifications
[oslo_messaging_notifications]
notification_topics = notifications
driver = noop

Make sure the driver option is set to "noop" by default it will be set too "messagingv2" and then restart the service and that should stop sending messages to the queue. You can then purge the "notifications.info<https://urldefense.com/v3/__http:/notifications.info__;!!Ci6f514n9QsL8ck!1JtoahRvJ7-o3UTgt10NXnicoDEJzvPdT32aMejFaeSUu2ObRSEFvEfDVSXCYHosug$>" queue for Nova or Neutron etc..

We only had the "message ready" when we had the setting for ceilometer set but was not using it. Also only purge a queue if it is for that reason. Do not purge the queue if it is for any other reason than that as it can cause issues.

Hope that

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200320/dccc6e04/attachment-0001.html>