[rabbitmq-discuss] Bug w/ Federated Queue's & Clustering

Josh West jsw at one.com
Wed Jan 22 03:09:52 GMT 2014

Hi folks,

I'm having an issue with RabbitMQ 3.2.2 (Erlang R15B01).

I have 3 clusters (2-nodes per cluster) configured for federation in a 
complete graph fashion (they all federate with each other).  Each 
cluster has a policy to federate queues with pattern ^cluster1.* (for 
cluster1), ^cluster2.* (for cluster2), and ^cluster3.* (for cluster3).  
So in other words, if clusters #2 or #3 have a queue with a name 
beginning with "cluster1", it will be federated (pulled down to) 
cluster1 upon request.  The policy for federation also has the attribute 
"ha-mode" set to "all", so that messages sent between clusters are not 
lost upon a failure.

The queue's I'm working with have the Auto Delete and Durable flags set.

Without much effort, I'm seeing errors on cluster1 after using the queue 
a few times.  The error is visible within the management console:

TypeError: Cannot read property 'ram_msg_count' of undefined

And federation from that point on for that queue fails.

When I do this complete graph scenario without making use of clusters I 
do not experience this problem.

I've seen mentions on the list that this was an issue with clusters and 
durable queues, but fixed in 3.2.1.  Perhaps it is still an issue?  Or 
still an issue just when federation is involved?


Josh West
One.com - http://www.one.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140121/c98a69f5/attachment.html>

More information about the rabbitmq-discuss mailing list