[rabbitmq-discuss] Federated Cluster Issue

Tue Apr 23 20:16:13 BST 2013

Simon,

I did not include the leading and trailing spaces when entering the pattern
in the management UI - just did it here for readability purposes.

I have the output of "rabbitmqctl report" from the 4 nodes in question (two
per cluster) - were there specific items that you wanted to look at (I'd
rather not share the entire output for security reasons)? I can see that
for the vhosts in question it is listing the federate-me policy (not sure
if that is what you were looking for).

Regards,

Richard

On Tue, Apr 23, 2013 at 7:36 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 23/04/13 15:28, Richard Raseley wrote:
>
>> Simon,
>>
>> Thank you for your reply.
>>
>> 1) I was trying to obfuscate my actual naming conventions - but they are
>> named in a similar manner. The general structure though is that in
>> cluster01 I have an exchange named something like "cluster01.topic" and
>> in the pattern field I put " ^cluster01\. " (basically everything in
>> preceeding the "." in the exchange name). Can you confirm that this
>> would be the correct pattern?
>>
>
> In the quotation marks you have leading and trailing spaces which would
> obviously stop the match from working. But other than that it looks fine.
>
>
>  2) I do not see "federate-me" show up in the management UI exchange list
>> - but I see the policy in the Admin section. Would it show up as a
>> discrete exchange itself?
>>
>
> Some federation-related infrastructure (including exchanges) would show up
> once federation starts, but if you don't see "federate-me" in the policy
> column for any exchange then the policy is not matching and nothing will
> happen.
>
> If you can post the results of "rabbitmqctl report" then I can look at why
> the policy pattern is not matching.
>
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130423/46ad4763/attachment.htm>