42 lines
1.2 KiB
Plaintext
42 lines
1.2 KiB
Plaintext
Release: RabbitMQ 2.8.1
|
|
|
|
Release Highlights
|
|
==================
|
|
|
|
server
|
|
------
|
|
bug fixes
|
|
- fixed cluster upgrades for RAM nodes
|
|
|
|
|
|
packaging
|
|
---------
|
|
bug fixes
|
|
- remove use of runuser for the SUSE RPM
|
|
- package rabbitmq-echopid.bat on Windows
|
|
|
|
|
|
management plugin
|
|
-----------------
|
|
bug fixes
|
|
- fixed web UI for users with only the 'management' tag
|
|
|
|
|
|
Upgrading
|
|
=========
|
|
To upgrade a non-clustered RabbitMQ from release 2.1.1 or later, simply install
|
|
the new version. All configuration and persistent message data is retained.
|
|
|
|
To upgrade a clustered RabbitMQ from release 2.1.1 or later, install the new
|
|
version on all the nodes and follow the instructions at
|
|
https://www.rabbitmq.com/clustering.html#upgrading .
|
|
|
|
To upgrade RabbitMQ from release 2.1.0, first upgrade to 2.1.1 (all data will be
|
|
retained), and then to the current version as described above.
|
|
|
|
When upgrading from RabbitMQ versions prior to 2.1.0, the existing data will be
|
|
moved to a backup location and a fresh, empty database will be created. A
|
|
warning is recorded in the logs. If your RabbitMQ installation contains
|
|
important data then we recommend you contact support at rabbitmq.com for
|
|
assistance with the upgrade.
|