[rabbitmq-discuss] Controlling upstream federation queue names
brendan at soundcloud.com
Fri Sep 21 14:52:34 BST 2012
Not entirely ideal .. I'd had visions of hacking this wee beastie to be
Going the route of changing exchange types and other upstream finger pokery
is not an option, unfortunately.
I'll stick to using an insentient shovel config, to ensure sharing upstream
queues in the meantime.
On Fri, Sep 21, 2012 at 12:11 PM, Simon MacMullen <simon at rabbitmq.com>wrote:
> On 21/09/12 09:01, Brendan Hay wrote:
> Say I have two downstream brokers connected to a single upstream,
>> upon which lives a single exchange.
>> Can I configure the plugin, to create the upstream federation queues,
>> with the same name so that they round-robin over messages coming
>> off the upstream exchange, to ensure messages are delivered to
>> _either_ of the downstream pair (rather than both)?
> Sort of.
> You could set the 'local_nodename' for each broker to the same value. They
> will both identify themselves the same way to the upstream, and thus share
> But they won't be aware of each other, and they will thus stomp on each
> other's bindings upstream. So that's not good.
> Maybe we need to separate the federation from the round-robinning? You
> could use the consistent hash exchange upstream as a source, and then bind
> two exchanges as local destinations to that, and then federate with those
> two exchanges. You won't share the upstream queues but you'll get a similar
> round-robinning effect (the difference being that if one link goes down
> messages will back up for it, rather than the other link taking the strain).
> Cheers, Simon
> Simon MacMullen
> RabbitMQ, VMware
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss