0x6e6562 at gmail.com
Thu Nov 1 07:22:08 GMT 2007
> I set up a cluster of 2 nodes - rabbit at node1 and rabbit at node2. Several producers will
> connect to either node and send a series of messages with topic hierarchy as routing key
> (for example, "a.b.c.d.e.f"). Consumers will also connect to either node and will register
> to receive some subset of what is being sent - in other words, for example, some of them
> will request "a.#" while others might want to get only "#.e.f". My goal is to make it
> happen if at least one of the nodes in the cluster is up and running. Both producers and
> consumers will know about existence of both cluster nodes, but they need to be able to
> randomly connect to either.
As far as I know, message queues are not yet fully clustered in
rabbitmq, meaning that you cannot yet transparently failover or
migrate a queue to a different node in the cluster. These queues are
visible from any node in the cluster however.
More information about the rabbitmq-discuss