Hi, in this change kolla-ansible removed setting the HA policies per default (along with why). TL;DR: The option `amqp_durable_queues` was not enabled on all openstack services, therefor HA queues do not make any sense (and actually actively make things worse). -- Felix Huettner From: Satish Patel <satish.txt@gmail.com> Sent: Friday, February 10, 2023 5:47 PM To: ozzzo@yahoo.com Cc: OpenStack Discuss <openstack-discuss@lists.openstack.org> Subject: Re: [kolla]RabbitMQ HA policies define Hi, I went through that doc because it always shows up first in google search :) My question was why the kolla default doesn't come with HA policies? I can surely add policy by myself and adjust requirements. I have also noticed without HA if any node fails then cause strange behavior in the entire cluster because of missing queues/data etc. Personally I hate HA because the majority of messages are stateless. In my experience HA is a little stable when it comes down to node failure but with performance big no. On Fri, Feb 10, 2023 at 11:15 AM Albert Braden <ozzzo@yahoo.com<mailto:ozzzo@yahoo.com>> wrote: This has been discussed at great length; here are a couple of links that lead to interesting threads: https://lists.openstack.org/pipermail/openstack-discuss/2021-November/026074.html<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openstack.org%2Fpipermail%2Fopenstack-discuss%2F2021-November%2F026074.html&data=05%7C01%7C%7C60f6a1fa3ee74910b82808db0b875351%7Cd04f47175a6e4b98b3f96918e0385f4c%7C0%7C0%7C638116448067688419%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2F2ewiZjNMTiVbO13shuiQBGgvHNWSAxw6cNCZ8GN2zo%3D&reserved=0> https://lists.openstack.org/pipermail/openstack-discuss/2020-August/016362.html<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openstack.org%2Fpipermail%2Fopenstack-discuss%2F2020-August%2F016362.html&data=05%7C01%7C%7C60f6a1fa3ee74910b82808db0b875351%7Cd04f47175a6e4b98b3f96918e0385f4c%7C0%7C0%7C638116448067688419%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Nivuk0mlqy%2F%2By8de3%2FiadRhB10XhSCgOeGszwdjRx0Q%3D&reserved=0> There used to be a useful document here: https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.openstack.org%2Fwiki%2FLarge_Scale_Configuration_Rabbit&data=05%7C01%7C%7C60f6a1fa3ee74910b82808db0b875351%7Cd04f47175a6e4b98b3f96918e0385f4c%7C0%7C0%7C638116448067688419%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U9w8zVCx1C%2BJxBIB5iP8nTxoI4FDHnv76ezQmOgYubw%3D&reserved=0> That link now points to the "Large Scale SIG" home page. Does anyone know where the useful RMQ document is? I assume that it is buried somewhere under "Large Scale Journey." The bottom line is that, by default, kolla-ansible enables replication but not durable-queues, which is an unstable configuration. I believe that this may have been fixed in a newer version; we are on Train. https://lists.openstack.org/pipermail/openstack-discuss/2020-August/016524.html<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openstack.org%2Fpipermail%2Fopenstack-discuss%2F2020-August%2F016524.html&data=05%7C01%7C%7C60f6a1fa3ee74910b82808db0b875351%7Cd04f47175a6e4b98b3f96918e0385f4c%7C0%7C0%7C638116448067688419%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=q%2FVgkhGeq0q59W9h5%2BCqKCt7lbgMh1RdIMbxE%2F0LBW4%3D&reserved=0> On Thursday, February 9, 2023, 10:48:11 PM EST, Satish Patel <satish.txt@gmail.com<mailto:satish.txt@gmail.com>> wrote: Folks, I have deployed 3 node kolla controllers and notice rabbitMQ doesn't have any HA policy for queues. when i rebooted one of the nodes and found some messages got lost. Any reason kolla doesn't use HA policies by default? If i want to add policies then where should i specify them or any doc you can point me to define policies. Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>.