[Openstack-operators] RabbitMQ issues since upgrading to Icehouse
sorrison at gmail.com
Mon Aug 25 23:17:49 UTC 2014
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?
More information about the OpenStack-operators