RabbitMQ 3.5
is released!
From this point, all new created clusters will be running
RabbitMQ 3.5.1.
Already running dedicated clusters can be upgraded
from our console page.
Important note: A full cluster restart is required for dedicated clusters with two nodes, Roaring Rabbit and larger. The cluster has to be restarted after the two nodes has been upgraded. If no downtime is possible do we recommend to upgrade by creating a new cluster and after that migrate to the new cluster, for example with help of off federation.
Go to the tab nodes and press Upgrade RabbitMQ.
Some of the new features in RabbitMQ 3.5
- The performance is improved, in particular are messages smaller than configurable size embedded in the queue index to reduce I/O and memory consumption.
- Priority queues are moved from an external plugin to the broker.
- The management web UI now shows more I/O statistics.
- Stability of clustering and autoheal partition handling is improved.
- .... and much more!
Read about all new features, performance improvements and bug fixes in RabbitMQ 3.5.0 release here .
Please email us at support@cloudamqp.com if you have any suggestions or feedback.
