<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>We bring up parallel infrastructure with a complete new cluster and gradually shift load to it using weighted routing.</div><div><br></div><div>This won't work for everybody, but we have designed our apps with this in mind.</div><div><br></div><div>Michael</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Chris Toomey <<a href="mailto:ctoomey@gmail.com">ctoomey@gmail.com</a>><br><span style="font-weight:bold">Reply-To: </span> rabbitmq <<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>><br><span style="font-weight:bold">Date: </span> Wed, 28 Nov 2012 19:55:31 -0500<br><span style="font-weight:bold">To: </span> Simon MacMullen <<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>><br><span style="font-weight:bold">Cc: </span> rabbitmq <<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>><br><span style="font-weight:bold">Subject: </span> Re: [rabbitmq-discuss] High availability questions<br></div><div><br></div>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></span></body></html>