[rabbitmq-discuss] Upgrading erlang, rabbitmq in a cluster.

[Matt Pietrek]

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.

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.

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.


On Mon, Nov 12, 2012 at 5:46 AM, Jean Paul Galea <ninuhadida at gmail.com>wrote:

> On 11/12/2012 01:38 PM, Emile Joubert wrote:
>
>> Hi,
>>
>> On 12/11/12 11:32, Jean Paul Galea wrote:
>>
>>> The question is, how do we keep these two nodes up to date with the
>>> latest versions, without suffering downtime?
>>>
>>
>> Details on how to upgrade a cluster are relevant in your case:
>> http://www.rabbitmq.com/**clustering.html#upgrading<http://www.rabbitmq.com/clustering.html#upgrading>
>>
>> It is not possible to upgrade a cluster without downtime, since all
>> nodes need to run the same version of RabbitMQ. All the nodes in the
>> cluster have to be shut down during upgrade, implying downtime.
>>
>> The interruptions can be as short as a server reboot. The impact of the
>> broker downtime can also be minimised by having publishers and consumers
>> automatically retry failed connections to the broker. Persistent
>> messages that exist in queues are preserved when the broker is upgraded,
>> so messages won't be lost due to upgrades.
>>
>>
>>
>> -Emile
>>
>
> OK, thanks for clarifying!
>
> ______________________________**_________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121112/ed3d43d6/attachment.htm>