[rabbitmq-discuss] Federation Issues

[Simon MacMullen]

I'm having trouble understanding exactly what problem you're describing. 
However, one thing leaps out at me: you've managed to (accidentally) 
make some of the queues used internally by federated exchanges 
*themselves* be federated with each other. This is likely to lead to odd 
behaviour. I can't guarantee that this is the problem you're describing, 
but it's certainly *a* problem.

You can either:

a) Rework your policies so that no policy which matches queues beginning 
with "^federation:" enables federation. (The policy "federation enabled" 
in the vhosts ControlCenter, MediaManager and Review could be changed to 
apply to "exchanges" rather than "all")

or

b) Upgrade to RabbitMQ 3.2.3, which prevents this confusing and 
unhelpful behaviour from happening.

Cheers, Simon

On 13/02/2014 6:51PM, Ganann, Kale wrote:
> I've attached the rabbitmqctl report for both nodes in this cluster.
> You're right, Simon, I meant exchanges.  Pardon the slip.  I'm
> trolling through the logs now looking for anything that might be
> relevant to throw your way.  Thanks, guys.
>
> Kale
>
>
> Thanks, Kale
>
> -----Original Message----- From: Simon MacMullen
> [mailto:simon at rabbitmq.com] Sent: Thursday, February 13, 2014 10:28
> AM To: Discussions about RabbitMQ Cc: Ganann, Kale Subject: Re:
> [rabbitmq-discuss] Federation Issues
>
> On 13/02/2014 04:51, Michael Klishin wrote:
>>> Any ideas what might be causing this?  Any logs or test I can run
>>> to narrow the scope of the field?
>>
>> Kale,
>>
>> Having RabbitMQ logs around the time the issue happens would be
>> very helpful.
>
> The output of "rabbitmqctl report" would also be useful (from each
> node in the federation).
>
> Also it would be good to understand whether you are talking about
> federated queues or exchanges. You say queues, but then you mention
> bindings and routing keys so I wonder if you mean exchanges?
>
> Cheers, Simon This communication contains information that is
> confidential, proprietary in nature, and may also be attorney-client
> privileged and/or work product privileged. It is for the exclusive
> use of the intended recipient(s). If you are not the intended
> recipient(s) or the person responsible for delivering it to the
> intended recipient(s), please note that any form of dissemination,
> distribution or copying of this communication is strictly prohibited
> and may be unlawful. If you have received this communication in
> error, please immediately notify the sender by replying to this
> message and delete this email immediately. Thank you for your
> cooperation.
>
> Please be advised that neither Altegrity, its affiliates, its
> employees or agents accept liability for any errors, omissions or
> damages caused by delays of receipt or by any virus infection in
> this message or its attachments, or which may otherwise arise as a
> result of this e-mail transmission.
>

-- 
Simon MacMullen
RabbitMQ, Pivotal