[rabbitmq-discuss] HA and database schema changes
Vlad Alexandru Ionescu
vlad at rabbitmq.com
Wed Sep 15 16:32:14 BST 2010
There is currently no easy way to migrate the database.
In general, it is advisable to use the same code which you first used to
create the exchanges, queues etc. on the new version of Rabbit to
reconstruct your setup.
In order to migrate messages, you would have to use the rabbitmq-shovel
plugin, which would consume messages from the old broker and would
publish them into the new one (you must come up with a sensible
configuration, depending on you setup).
Hope that answers your question.
On 09/14/2010 09:28 PM, Steve Haneman wrote:
> I was looking over the release notes for "Release: RabbitMQ 2.0.0" and
> saw the following:
> The database schema and the format in which persistent messages are
> stored have both changed since the last release (1.8.1). When
> starting, the RabbitMQ server will detect the existence of an old
> database and will move it to a backup location, before creating a
> fresh, empty database, and will log a warning. If your RabbitMQ
> installation contains important data then we recommend you contact
> support at ... for assistance with the upgrade.
> We are considering deploying a HA RabbitMQ cluster with Pacemaker and
> DRBD. HA is very important for us.
> If there is a database schema change in the future, specifically what
> is the process for the upgrade and how does it affect HA during the
> Also during the upgrade, how do we maintain durable exchanges and queues?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss