Hi Sam, I've been tracking down other bugs with oslo.messaging + rabbit: My problem was publishers may deliver messages to the void if rabbit restarts. See https://bugs.launchpad.net/oslo.messaging/+bug/1338732 and https://review.openstack.org/#/c/109373/. Cheers, -- Noel On Mon, Aug 25, 2014 at 4:17 PM, Sam Morrison <sorrison at gmail.com> wrote: > Hi, > > Since upgrading to Icehouse we have seen increased issues with messaging > relating to RabbitMQ. > > 1. We often get reply_xxxxxx queues starting to fill up with unacked > messages. To fix this we need to restart the offending service. Usually > nova-api or nova-compute. > > 2. If you kill a node so as to force an *ungraceful* disconnect of rabbit > the connection “object?” still sticks around in rabbit. Starting the > service again means there are now 2 consumers. The new one and the phantom > old one. This then leads to messages piling up in the unacked queue. This > feels like a rabbit bug to me but just thought I’d mention it here too. > > > We have have a setup that includes icehouse computes and havana computes > in the same cloud and we only see this on the icehouse computes. This is > using Trusty and RabbitMQ 3.3.4 > > > Has anyone seen anything like this too? > > Thanks, > Sam > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140902/9d66dccf/attachment.html>