[rabbitmq-discuss] High availability questions

[Chris Toomey]

Thanks Simon.

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 :-(.

What kinds of solutions are people using for that problem?

Chris

On Wed, Nov 28, 2012 at 2:31 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 27/11/12 21:54, Chris Toomey wrote:
>
>> I'm fairly new to RabbitMQ and we're in the process of setting up our
>> production RabbitMQ servers.  We're going to set up a server cluster and
>> will use mirrored queues for high availability. I've read through the
>> great documentation you guys have on these topics but still have some
>> questions.
>>
>> 1) Given the clustered server redundancy and mirrored queues, is there
>> any reason to still make exchanges/queues/messages durable?  Is it just
>> to protect against the case when all nodes in the cluster fail?
>>
>
> Or are deliberately stopped.
>
>
>  2) In order to update the server configuration, it's necessary to
>> restart, correct?  If so, what's the best way to accomplish config.
>> updates across a cluster while minimizing downtime and loss of redundancy?
>>
>
> You can update each node's config one at a time, and restart them all
> individually.
>
>
>  3) Same question for upgrading to a newer version of RabbitMQ?
>>
>
> In order to update the version of RabbitMQ (or Erlang for that matter) you
> need to stop the entire cluster I'm afraid.
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121128/970c508c/attachment.htm>