[rabbitmq-discuss] Federation in a cluster

[Cao, Yican - 0551 - MITLL]

Thanks much Simon, 

You are saying I only need to declare one setting in E? 
ie. 
in E:
rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://A", "expires":3600}'
rabbitmqctl set_policy...
....

Now, it comes that if A which is my upstream fails, what would happen? [A, B, C] is running with HAQ (active/active).
Do I just lost federation?
If not, how does E handle this in case of 
1) A is a master
2) A is a slave 
?

[E, F] also runs HAQ cluster, what if E dies, how to config F continue to perform as down-stream nodes as HAQ suppose to do ? Can we achieve this?

Thanks.


Yican




On Jan 29, 2013, at 11:27 AM, Simon MacMullen wrote:

> You don't need to declare the same parameters and policies in E and F, 
> they're cluster-wide.
> 
> You should note that if you specify nodes from the same cluster as 
> separate upstreams then the federated exchange will attempt to consume 
> from them all simultaneously - this might break message ordering. So you 
> would normally add each cluster once.
> 
> At the moment there's no way to say "all these upstreams are in the same 
> cluster, just ensure you use one of them" although we hope to add this 
> in a future release.
> 
> Cheers, Simon
> 
> On 28/01/13 21:36, Cao, Yican - 0551 - MITLL wrote:
>> Hi,
>> 
>> 
>> In federation document, it says:
>> "When using a federation in a cluster, all the nodes of the cluster must have the federation plugin installed. ..."
>> 
>> I have 2 clustered HAQ nodes [A, B, C] and [E, F].
>> [A, B, C] is clustered and so does [E, F].
>> 
>> Do I have to:
>> in E:
>> rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://A", "expires":3600}'
>> rabbitmqctl set_policy...
>> ....
>> rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://B", "expires":3600}'
>> rabbitmqctl set_policy...
>> ....
>> rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://C", "expires":3600}'
>> rabbitmqctl set_policy...
>> ....
>> 
>> 
>> and do the same in F:
>> rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://A", "expires":3600}'
>> rabbitmqctl set_policy...
>> ....
>> rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://B", "expires":3600}'
>> rabbitmqctl set_policy...
>> ....
>> rabbitmqctl set_parameter federation-upstream my-upstream '{"uri":"amqp://C", "expires":3600}'
>> rabbitmqctl set_policy...
>> ....
>> 
>> ?
>> 
>> 
>> If I want to use Pair of federated exchanges in your example topologies,
>> 
>> Shall I setup same in A, B and C?
>> 
>> 
>> Thanks.
>> 
>> 
>> Yican Cao
>> 
>> 
>> 
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> 
> 
> 
> -- 
> Simon MacMullen
> RabbitMQ, VMware

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130129/0073dcf4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5652 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130129/0073dcf4/attachment.bin>