[rabbitmq-discuss] Federation Configuration and Duplicate Messages

Letourneau, John P (John) john.letourneau at alcatel-lucent.com
Wed Jan 4 12:27:09 GMT 2012


Simone,
Ah, sorry I missed the suggestion to configure a fully interconnected network.
Yes that would work. However it becomes an administrative nightmare as nodes are added to the network.
Therefore I don't think this is viable.
-John

From: Busoli, Simone [mailto:Simone.Busoli at ferrari.com]
Sent: Wednesday, January 04, 2012 7:02 AM
To: Letourneau, John P (John); Simone Busoli
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: RE: [rabbitmq-discuss] Federation Configuration and Duplicate Messages

That's true with your current configuration, but if you federate each broker with the other two like I suggested it is going to work.

From: Letourneau, John P (John) [mailto:john.letourneau at alcatel-lucent.com]
Sent: mercoledì 4 gennaio 2012 12:54
To: Simone Busoli
Cc: Busoli, Simone; rabbitmq-discuss at lists.rabbitmq.com
Subject: RE: [rabbitmq-discuss] Federation Configuration and Duplicate Messages

Simone,
If I were to set hops=1, then a message posted at N1 would go to N2 but will NOT go to N3. This has been verified.
Similarly a message posted at N3 would go to N2 but NOT go to N1.

-John

From: Simone Busoli [mailto:simone.busoli at gmail.com]
Sent: Tuesday, January 03, 2012 3:16 PM
To: Letourneau, John P (John)
Cc: Busoli, Simone; rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Federation Configuration and Duplicate Messages


Inline

On Jan 3, 2012 4:52 PM, "Letourneau, John P (John)" <john.letourneau at alcatel-lucent.com<mailto:john.letourneau at alcatel-lucent.com>> wrote:
>
> Well, perhaps a bit more about my configuration 8-)
>
> 3 nodes...call them N1, N2, N3.
>
> On each I have federation configured.
>
> N2 - exchange log, connects to N1/log and N3/log
>
> N3 - exchange log, connects to N2/log
>
> Right now I cannot seem to have the N1 exchange log connect to N2/log; will need to find out why sometime.
>
> I do it this way so that regardless of where the producer of the log message is, everyone everywhere will see it.

If this is your aim, can't you simply federate the log exchange on each broker with the other two and set max hops to 1?

>
>
>
> Each layer in the hierarchy only knows about nodes in adjacent layers...N2 being the busy one with a layer above and below.
>
> If everyone has hops=1, sending a log message to N1/log will only go to N2 and not N3 [this is correct].
>
> Setting hops=4, sending a log to N1/log will go to N2 and N3...it will also be returned to N2 thus a consumer on N2 will see the original msg AND the one sent via N2/N3 federation link. Also N3 sees it twice also for a total of once on N1, twice on N2, and twice on N3...the message took a total of 4 hops.
>
>
>
> So, this is what I mean by 'one might expect' 8-)
>
> -John
>
>
>
> From: Busoli, Simone [mailto:Simone.Busoli at ferrari.com<mailto:Simone.Busoli at ferrari.com>]
> Sent: Tuesday, January 03, 2012 10:23 AM
> To: Letourneau, John P (John); rabbitmq-discuss at lists.rabbitmq.com<mailto:rabbitmq-discuss at lists.rabbitmq.com>
> Subject: RE: Federation Configuration and Duplicate Messages
>
>
>
> Hi John, I'm not sure about this:
>
>
>
> As one might expect, this sometimes results in the message being seen >1 time at some clients.
>
>
>
> It shouldn't be the expected behavior except for certain scenarios (i.e. disconnection of the brokers). Am I missing something perhaps?
>
> _________________________________________________________________________________________________________________
> 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<mailto:rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

_________________________________________________________________________________________________________________
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.
_________________________________________________________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120104/5bba45c9/attachment.htm>


More information about the rabbitmq-discuss mailing list