Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

___ >> >> Kris Lindgren >> >> Senior Linux Systems Engineer >> >> GoDaddy >> >> >> >> *From: *Dmitry Mescheryakov <dmescherya...@mirantis.com> >> *Date: *Thursday, July 28, 2016 at 6:17 AM >> *T

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

*Date: *Thursday, July 28, 2016 at 6:17 AM > *To: *Sam Morrison <sorri...@gmail.com> > *Cc: *OpenStack Operators <openstack-operators@lists.openstack.org> > *Subject: *Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues > moving to Liberty > > > >

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

> On 28 Jul 2016, at 10:17 PM, Dmitry Mescheryakov > wrote: > > > > 2016-07-27 2:20 GMT+03:00 Sam Morrison >: > >> On 27 Jul 2016, at 4:05 AM, Dmitry Mescheryakov >

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

k-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty 2016-07-27 2:20 GMT+03:00 Sam Morrison <sorri...@gmail.com<mailto:sorri...@gmail.com>>: On 27 Jul 2016, at 4:05 AM, Dmitry Mescheryakov <dmescherya...@mirantis.com<mailto:dmescherya...@mirantis.com>> wrote:

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

nStack service needs to clean up on shutdown in some > external place. > > Thanks, > > Dmitry > >> >> Thanks, >> Kevin >> >> From: Dmitry Mescheryakov [dmescherya...@mirantis.com] >> Sent: Tuesday, July 26, 2016 11:

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

metadata agents do not stop RPC server. > > I am not sure how that relates to Kubernates, as I not much familiar with > it. > > Thanks, > > Dmitry > > >> >> Thanks, >> Kevin >> ------ >> *From:* Dmitry Mescheryakov [dmeschery

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

2016-07-27 2:20 GMT+03:00 Sam Morrison : > > On 27 Jul 2016, at 4:05 AM, Dmitry Mescheryakov < > dmescherya...@mirantis.com> wrote: > > > > 2016-07-26 2:15 GMT+03:00 Sam Morrison : > >> The queue TTL happens on reply queues and fanout queues. I don’t think

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

> On 27 Jul 2016, at 4:05 AM, Dmitry Mescheryakov > wrote: > > > > 2016-07-26 2:15 GMT+03:00 Sam Morrison >: > The queue TTL happens on reply queues and fanout queues. I don’t think it > should happen on fanout

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty 2016-07-25 18:47 GMT+03:00 Fox, Kevin M <kevin@pnnl.gov<mailto:kevin@pnnl.gov>>: Ah. Interesting. The graceful shutdown would really help the Kubernetes situation too. Kubernetes can do easy roll

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

2016-07-26 2:15 GMT+03:00 Sam Morrison : > The queue TTL happens on reply queues and fanout queues. I don’t think it > should happen on fanout queues. They should auto delete. I can understand > the reason for having them on reply queues though so maybe that would be a > way

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

Dmitry > > Thanks, > Kevin > -- > *From:* Dmitry Mescheryakov [dmescherya...@mirantis.com] > *Sent:* Monday, July 25, 2016 3:47 AM > *To:* Sam Morrison > *Cc:* OpenStack Operators > *Subject:* Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues > moving to

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

The queue TTL happens on reply queues and fanout queues. I don’t think it should happen on fanout queues. They should auto delete. I can understand the reason for having them on reply queues though so maybe that would be a way to forward? Or am I missing something and it is needed on fanout

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

To: OpenStack Operators Subject: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty We recently upgraded to Liberty and have come across some issues with queue build ups. This is due to changes in rabbit to set queue expiries as opposed to queue auto delete. See https

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

it have to be added to all projects using it? Thanks, Kevin From: Dmitry Mescheryakov [dmescherya...@mirantis.com] Sent: Monday, July 25, 2016 3:47 AM To: Sam Morrison Cc: OpenStack Operators Subject: Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

I have filed a bug in oslo.messaging to track the issue [1] and my colleague Kirill Bespalov posted a fix for it [2]. We have checked the fix and it is working for neutron-server, l3-agent and dhcp-agent. It does not work for openvswitch-agent and metadata-agent meaning they do not stop RPC

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

Sam, For your case I would suggest to lower rabbit_transient_queues_ttl until you are comfortable with volume of messages which comes during that time. Setting the parameter to 1 will essentially replicate bahaviour of auto_delete queues. But I would suggest not to set it that low, as otherwise

[Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

We recently upgraded to Liberty and have come across some issues with queue build ups. This is due to changes in rabbit to set queue expiries as opposed to queue auto delete. See https://bugs.launchpad.net/oslo.messaging/+bug/1515278 for more information. The fix for this bug is in liberty