[rabbitmq-discuss] Upgrade 2.7.1 RabbitMQ cluster to 2.8.1 version

[Brendan Hay]

Eslam, what sort of state do you need to transfer from the old cluster to
the new cluster?

For messages, you will need to use shovel or a simple client to consume
messages from your old cluster and publish them to your new cluster.

If it's bindings and so on, ideally these are codified in your client code
anyway and will be established when the clients connect to the new cluster.
If this isn't the case, you can use the 'import/export definitions'
functionality from the management interface overview, with possible hand
tweaks to the exported json to ensure queue distribution/node locality
before importing to the new cluster.

Be aware that if you go the route of copying the /var/lib/rabbitmq
directory as you suggested, the source and destination hostnames of the
machines you're copying from/to need to be identical due to mnesia
requirements,

- Brendan


On Thu, Apr 5, 2012 at 9:24 PM, Matthias Radestock <matthias at rabbitmq.com>wrote:

> Eslam,
>
>
> On 05/04/12 20:19, Eslam Mamdouh wrote:
>
>> mmh, i see but what about old cluster data that exists in
>> /var/lib/rabbitmq , should i have a copy of them in the new cluster with
>> version 2.8.1-1
>>
>
> Yes, you could set up the new cluster with a copy of the old cluster's
> data as a starting point. Though you do of course need to consider what to
> do about any changes made to such data between the time the copy is taken
> and the switch to the new cluster takes place.
>
>
> Matthias.
> ______________________________**_________________
> 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/20120406/435901ff/attachment.htm>