[rabbitmq-discuss] Federation and QoS
simon at rabbitmq.com
Tue Jan 31 11:11:45 GMT 2012
It's important to remember that the RabbitMQ federation plugin federates
*exchanges*, not queues. The idea is that any message that gets
federated will get sent to all the brokers in the federation.
If you want to ensure that each message only gets consumed in one broker
you will need to send messages around using the shovel at the moment by
having multiple shovels consume from a single queue.
On 31/01/12 05:50, James Aimonetti wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> We have a federated setup that we're testing, and I'm wondering about
> queues and de-duping.
> We have a number of named queues that have multiple consumers attached,
> with QoS to 1 so things are round-robined among those consumers.
> Assuming bi-directional federation, and consumers on both brokers, will
> it be possible that a publisher's payload on broker1 will reach both a
> consumer on broker1 and be published to broker2 to be consumed there as
> If not, is there a way to figure out whether to actually federate the
> message across brokers? Any pointers, in general, on how messaging
> changes from non-federated to federated, given non-federated messaging
> We're really excited to start pushing the federation out, but we need to
> get these patterns solidified.
> - --
> James Aimonetti
> Distributed Systems Engineer / DJ MC_
> 2600hz | http://2600hz.com
> sip:james at 2600hz.com
> tel: 415.886.7905
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss