[rabbitmq-discuss] Pathological dead queue behavior in a cluster.

Jason J. W. Williams jasonjwwilliams at gmail.com
Wed Mar 30 22:58:23 BST 2011


>
> Very interesting. I assume the exchange in a fanout exchange (I see no
> routing key in your list_bindings output). When in this "broken" state,
> what happens if you publish to the queue with mandatory set?


The exchange is a direct exchange. With mandatory set it doesn't raise any
exceptions.

I'm noticing the output of list_bindings is different after the node restart
and then after the redeclare.

Before Restart:

Listing bindings ...
exchange cluster_test queue cluster_test []
cluster_test exchange cluster_test queue cluster_test []
...done.

While Node Is Down:
Listing bindings ...
...done.

After Restart:

Listing bindings ...
exchange cluster_test queue cluster_test []
...done.


It looks like there's an extra binding that doesn't get recreated.

-J
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110330/772f004a/attachment-0001.htm>


More information about the rabbitmq-discuss mailing list