Thanks Simon.<div><br></div><div>That's unfortunate about having to shut down the whole cluster to upgrade it -- it means that our applications will need to have some additional HA queueing mechanism�upstream�to buffer up the messages to be published during the downtime :-(.</div>
<div><br></div><div>What kinds of solutions are people using for that problem?</div><div><br></div><div>Chris<br><br><div class="gmail_quote">On Wed, Nov 28, 2012 at 2:31 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="im">On 27/11/12 21:54, Chris Toomey wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm fairly new to RabbitMQ and we're in the process of setting up our<br>
production RabbitMQ servers. �We're going to set up a server cluster and<br>
will use mirrored queues for high availability. I've read through the<br>
great documentation you guys have on these topics but still have some<br>
questions.<br>
<br>
1) Given the clustered server redundancy and mirrored queues, is there<br>
any reason to still make exchanges/queues/messages durable? �Is it just<br>
to protect against the case when all nodes in the cluster fail?<br>
</blockquote>
<br></div>
Or are deliberately stopped.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) In order to update the server configuration, it's necessary to<br>
restart, correct? �If so, what's the best way to accomplish config.<br>
updates across a cluster while minimizing downtime and loss of redundancy?<br>
</blockquote>
<br></div>
You can update each node's config one at a time, and restart them all individually.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3) Same question for upgrading to a newer version of RabbitMQ?<br>
</blockquote>
<br></div>
In order to update the version of RabbitMQ (or Erlang for that matter) you need to stop the entire cluster I'm afraid.<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br></div>