[rabbitmq-discuss] Cluster capability?

[Paul Bell]

Hi Michael,

I think we're close to the answer I need in order to think about this more
clearly. So, if I have two HA clusters connected via Shovel and I want to
publish a message that will be propagated not only to the local nodes in
the cluster, but also across the Shovel to all of the nodes in the remote
cluster, to where must I publish?

Can my component simply publish to any exchange on its node, or must it
publish twice, once to any exchange on its node and again to a "special"
exchange which represents one end of the Shovel? (I don't really mean "any"
exchange; just trying to make a distinction between a local exchange I've
defined and which is mirrored across the local cluster, and what I suppose
to be a different exchange that is one end of the Shovel. I may be way out
of my depth in making this distinction).

I will look at exchange confederation as you suggest.

Thanks for your help.

-Paul




On Sun, Dec 22, 2013 at 12:56 PM, Michael Klishin <
michael.s.klishin at gmail.com> wrote:

> 2013/12/22 Paul Bell <arachweb at gmail.com>
>
>> I was looking at http://www.rabbitmq.com/shovel.html when your post
>> appeared. The language on that page speaks in terms of source and
>> destination brokers. Does this mean that Shovel is one way? Put otherwise,
>> if Cluster 1 is source and Cluster 2 destination, can Cluster 2 also act as
>> source; or would such a configuration/use require 2 Shovels, one for each
>> direction?
>>
>
> I believe it can but if you are looking for more sophisticated replication
> setups,
> take a look at federated exchanges:
>
> http://www.rabbitmq.com/federated-exchanges.html
>
> (note the max-hops setting)
>
> --
> MK
>
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131225/d5260bc5/attachment.html>