Last checked and updated on 01 May 2026What Is New in RabbitMQ 2.8
RabbitMQ 2.8 is a significant release focused on core stability and operational enhancements. It introduces new exchange types, improves the management UI, and addresses numerous bugs from previous versions.
| Category | Key Changes |
|---|---|
| New Features | New exchange types, Enhanced management plugin features |
| Improvements | Performance optimizations, Better memory handling, UI/UX updates |
| Bug Fixes | Fixes for message persistence, clustering issues, and connection handling |
| Deprecations | Marking older MQTT and STOMP plugin versions for removal |
What new exchange types were added?
RabbitMQ 2.8 introduced the Consistent Hash Exchange. This exchange type routes messages to queues based on a consistent hashing algorithm, which is great for achieving even load distribution.
In practice, this means you can avoid hot-spotting where one queue gets overwhelmed. Instead, messages are distributed more evenly across multiple queues based on a routing key, improving overall throughput for certain workloads.
How was the management UI improved?
The management plugin received several usability upgrades. The UI now provides more granular metrics per queue and connection, making it easier to pinpoint bottlenecks.
You'll also find better visualization for message rates and consumer activity. This matters because it reduces the time needed for debugging and performance tuning in production environments.
Were there any critical bug fixes?
Yes, several edge cases around message persistence and cluster failover were resolved. One notable fix addressed an issue where under heavy load, some messages could be lost during a node failure.
Another fix improved the handling of long-lived connections, preventing a memory leak that could gradually consume broker resources. These fixes directly impact reliability for high-throughput systems.
What should I know about performance changes?
This release includes optimizations for internal scheduling and garbage collection. The Erlang VM parameters were tuned for better latency under load, especially for scenarios with many concurrent connections.
You might see lower CPU usage during peak traffic. The changes are mostly under the hood, but they contribute to a more stable and predictable broker performance.
FAQ
Is the Consistent Hash Exchange production-ready in 2.8?
Yes, it is considered stable. However, test it with your specific workload patterns as the hashing behavior might affect your routing logic.
Does upgrading to 2.8 require a cluster-wide restart?
Yes, a full cluster restart is required for this upgrade. Plan for a maintenance window as the binary protocol version was incremented.
Were any security vulnerabilities patched in this release?
This release primarily focused on features and stability. Always check the official advisories for your specific version, but no major CVEs were announced for 2.8 itself.
Can I upgrade directly from version 2.7?
Yes, the upgrade path from 2.7 to 2.8 is direct and supported. Always backup your definitions and message stores before proceeding.
Are the deprecated MQTT features still available?
They are available but will generate warnings. Start planning to migrate to the newer, supported versions of the plugins as they will be removed in a future release.