[rabbitmq-discuss] Federation Duplicates and Filtering

[Dann]

Thanks!  Is there a release date for 3.3.0?  I hope it is also in 3.3.0. :-)


On Mon, Jan 27, 2014 at 9:48 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 27/01/2014 16:36, Dann wrote:
>
>> How hard would it be to implement an option for federation that would
>> use the x-received-from header to know if a message came from an
>> upstream and then not send it back that way?
>>
>
> It's on the TODO list. It *might* be in 3.3.0. (I would certainly like it
> to be.)
>
>
>  Everything sounds simple in my mind but I am sure there are some
>> interesting gotchas with this option.
>>
>
> It's a bit harder than it looks, yes. The problem is that there are two
> notions of node identity in federation - what a node knows itself as (the
> local_nodename, defaulting to but not necessarily the hostname) and what
> other nodes know it as (the DNS name, ending up in the URI). Maybe if you
> are lucky then the two coincide, but I would not want to assume that. Plus
> federation links really connect clusters, which don't have DNS names
> anyway. And we want to drop messages at the upstream, for efficiency, so we
> only have the local_nodename to go on - but x-received-from contains URIs.
>
> So we need to sort that lot out before it can happen. Not impossible, but
> just a bit fiddly.
>
> Cheers, Simon
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140127/e1ab31e8/attachment.html>