[rabbitmq-discuss] Symmetric federation behavior

Simon MacMullen simon at rabbitmq.com
Thu Mar 1 14:16:39 GMT 2012


The best workaround I can offer is to only use asymmetric federation - 
i.e. have separate upstream and downstream exchanges and consume from 
both in any given broker.

Cheers, Simon

On 01/03/12 14:10, Busoli, Simone wrote:
> Too bad that I didn't realize this was the case earlier, as this is a real showstopper because of bandwidth consumption.
> Any chance, by any means, we can have a fix for this or a feasible workaround?
>
> -----Original Message-----
> From: Simon MacMullen [mailto:simon at rabbitmq.com]
> Sent: giovedì 1 marzo 2012 14:55
> To: Busoli, Simone
> Cc: rabbitmq-discuss at lists.rabbitmq.com
> Subject: Re: [rabbitmq-discuss] Symmetric federation behavior
>
> Yeah, I'm afraid that's the case. The existing design puts all the smarts in the downstream; therefore the message can only be thrown away once it's already gone over the gap.
>
> We will revisit this at some point.
>
> Cheers, Simon
>
> On 01/03/12 13:27, Busoli, Simone wrote:
>> Hello,
>>
>> I've set up a symmetric federation between two brokers A and B, that
>> is, an exchange on one broker acts as the upstream for one on the
>> other broker with the same name and vice versa.
>>
>> To prevent messages from going into an infinite loop I've set max_hops
>> to 1, but I am under the impression that messages published to broker
>> A and then proxied to broker B are somehow proxied back once again to
>> broker A and just then ignored because of the max_hops setting.
>>
>> Is this behavior expected? Our rationale for using this kind of
>> symmetrically configured federation is twofold: first to prevent
>> messages to go into loops and secondly to conserve bandwidth by
>> preventing messages to roundtrip from A to B and back, and this second
>> aspect doesn't seem to work correctly right now.
>>
>> Thanks
>>
>> ______________________________________________________________________
>> ___________________________________________
>> Questo messaggio e da intendersi esclusivamente ad uso del
>> destinatario e puo contenere informazioni che sono di natura
>> privilegiata, confidenziale o non divulgabile secondo le leggi
>> vigenti. Se il lettore del presente messaggio non e il destinatario
>> designato, o il dipendente/agente responsabile per la consegna del
>> messaggio al destinatario designato, si informa che ogni
>> disseminazione, distribuzione o copiatura di questa comunicazione e
>> strettamente proibita anche ai sensi del decreto legislativo 196/03 .
>> Se avete ricevuto questo messaggio per errore, vi preghiamo di
>> notificarcelo immediatamente a mezzo e-mail di risposta e
>> successivamente di procedere alla cancellazione di questa e-mail e relativi allegati dal vostro sistema.
>> ______________________________________________________________________
>> ___________________________________________
>> This message is intended only for the use of the addressee and may
>> contain information that is privileged, confidential and exempt from
>> disclosure under applicable law. If the reader of this message is not
>> the intended recipient, or the employee or agent responsible for
>> delivering the message to the intended recipient, you are hereby
>> notified that any dissemination, distribution or copying of this
>> communication is strictly prohibited. If you have received this e-mail
>> in error, please notify us immediately by return e-mail and delete
>> this e-mail and all attachments from your system.
>> ______________________________________________________________________
>> ___________________________________________
>>
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
> _________________________________________________________________________________________________________________
> Questo messaggio è da intendersi esclusivamente ad uso del destinatario e può contenere informazioni che sono di natura privilegiata, confidenziale
> o non divulgabile secondo le leggi vigenti. Se il lettore del presente messaggio non è il destinatario designato, o il dipendente/agente responsabile
> per la consegna del messaggio al destinatario designato, si informa che ogni disseminazione, distribuzione o copiatura di questa comunicazione è
> strettamente proibita anche ai sensi del decreto legislativo 196/03 . Se avete ricevuto questo messaggio per errore, vi preghiamo di notificarcelo
> immediatamente a mezzo e-mail di risposta e successivamente di procedere alla cancellazione di questa e-mail e relativi allegati dal vostro sistema.
> _________________________________________________________________________________________________________________
> This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from
> disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the
> message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from
> your system.
> _________________________________________________________________________________________________________________
>
>


-- 
Simon MacMullen
RabbitMQ, VMware


More information about the rabbitmq-discuss mailing list