WRT the zero consumer queues, in the past I've just had a cron job that checks for this and deletes queues that have messages no consumers.
> On Dec 4, 2014, at 12:23 PM, Fischer, Matt <[email protected]> > wrote: > > What RabbitMQ optimizations are people making with respect to OpenStack? > We’ve started looking into how we can optimize our rabbit cluster to make it > more robust and less resource intensive. One thing that seems to happen is > that the number of messages we have slowly grows over time because we have > messages not being consumed. We’re going to try two things to remedy this and > I’d like to get feedback on them: > The first thing we’d like to do is set a TTL on the OpenStack related queues. > We’ve tossed around some numbers like a 60 minute TTL or even a 5 minute one. > Has anyone tried this? We’d like to get a good estimate as to a time past > which the operation has likely failed anyway or the client is no longer > listening. (For example if the VM spins up 60 minutes after it was requested, > your client has likely given up and tried it again). > Another reason we can get messages is that we sometimes have queues with no > consumers. These tend to be auto-delete reply queues. We’re planning on at > least monitoring these and then trying to figure out why they’re happening. > Has anyone else seen these and have advice or a solution? > Finally we’re looking into is ensuring queues are synced before we a node > rejoins the rabbit cluster. We’ve found that at least some of the queues some > of the time do not synchronize. We’re not using auto sync due to the number > of queues. What’s the community opinion on this? > > This E-mail and any of its attachments may contain Time Warner Cable > proprietary information, which is privileged, confidential, or subject to > copyright belonging to Time Warner Cable. This E-mail is intended solely for > the use of the individual or entity to which it is addressed. If you are not > the intended recipient of this E-mail, you are hereby notified that any > dissemination, distribution, copying, or action taken in relation to the > contents of and attachments to this E-mail is strictly prohibited and may be > unlawful. If you have received this E-mail in error, please notify the sender > immediately and permanently delete the original and any copy of this E-mail > and any printout. > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
