[rabbitmq-discuss] Upgrading RabbitMQ cluster

[Michael Klishin]

Viraj Gupte:

> {"init terminating in do_boot",{function_clause,[{lists,usplit_1,['rabbit at crxv10','rabbit at crxv11',{['rabbit at crxv10','rabbit at crxv11'],['rabbit at crxv10']},[],[]]},{rabbit_upgrade,maybe_upgrade_mnesia,0},{rabbit,prepare,0},{init,eval_script,8},{init,do_boot,3}]}}

I suspect that the upgrade step in the release you are trying assumes a different
[internal] database schema from what you actually have after upgrading to 3.1.

Without writing code to perform a reverse migration, broker won't start. Unfortunately,
some migrations simply cannot be reversed (e.g. if a column was removed
from a table).

See http://hg.rabbitmq.com/rabbitmq-server/file/5740b52b882e/src/rabbit_upgrade.erl
to learn what's involved in a database upgrade.

MK



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130904/992e8a30/attachment.pgp>