For what it's worth, we have a system here that allows us to upgrade clusters without downtime. It works for us, but may or may not be workable for other teams.<br><br>Short synopsis is that our cluster is behind a VIP. When we want to upgrade a cluster, we spin up an alternate cluster and switch the VIP over to the alternate cluster. Meanwhile, we have tooling that moves messages between clusters. When the 'master' cluster's update is done, we reverse the process.<br>
<br>This does require that your clients be tolerant to dropped connections. There's a lot of details not covered in the above description but it gives the basic gist of it.<br><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Nov 12, 2012 at 5:46 AM, Jean Paul Galea <span dir="ltr"><<a href="mailto:ninuhadida@gmail.com" target="_blank">ninuhadida@gmail.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="im">On 11/12/2012 01:38 PM, Emile Joubert wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
On 12/11/12 11:32, Jean Paul Galea wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The question is, how do we keep these two nodes up to date with the<br>
latest versions, without suffering downtime?<br>
</blockquote>
<br>
Details on how to upgrade a cluster are relevant in your case:<br>
<a href="http://www.rabbitmq.com/clustering.html#upgrading" target="_blank">http://www.rabbitmq.com/<u></u>clustering.html#upgrading</a><br>
<br>
It is not possible to upgrade a cluster without downtime, since all<br>
nodes need to run the same version of RabbitMQ. All the nodes in the<br>
cluster have to be shut down during upgrade, implying downtime.<br>
<br>
The interruptions can be as short as a server reboot. The impact of the<br>
broker downtime can also be minimised by having publishers and consumers<br>
automatically retry failed connections to the broker. Persistent<br>
messages that exist in queues are preserved when the broker is upgraded,<br>
so messages won't be lost due to upgrades.<br>
<br>
<br>
<br>
-Emile<br>
</blockquote>
<br></div>
OK, thanks for clarifying!<div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>