<div dir="ltr">Yeah, thats what I realised when I did the upgrade, the type x-federation wasnt there. I had to set a policy to make it work</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Oct 21, 2013 at 5:45 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 17/10/2013 3:41PM, Viraj Gupte wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi All,<br>
I have two rabbitmq clusters A and B connected to each other via<br>
federation plugin in bidirectional manner.Both of them run version 2.8.7.<br>
I am planning to upgrade cluster A to 3.1.0 to check how federation<br>
works with the cluster with 2.8.7 version(cluster B).<br>
What should be my approach so as to keep the federation config intact on<br>
cluster A along with messages and queues<br>
</blockquote>
<br></div></div>
Federation does not require that brokers be the same version. So you can upgrade clusters A and B at different times.<br>
<br>
Note that the federation configuration mechanism changed in 3.0.0 so you will need to redo the federation config in each cluster as you upgrade it; see <a href="http://www.rabbitmq.com/blog/2012/11/19/breaking-things-with-rabbitmq-3-0/" target="_blank">http://www.rabbitmq.com/blog/<u></u>2012/11/19/breaking-things-<u></u>with-rabbitmq-3-0/</a><br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, Pivotal<br>
</font></span></blockquote></div><br></div>