Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.11.0.md

RabbitMQ 3.11 is a new feature release. This release series . This release includes several new features and optimizations, graduates (makes mandatory) a number of feature flags, bumps minimum required version to Erlang 25 for ARM64 CPU feature parity. The areas that have seen the biggest improvements in this release are Streams and the RabbitMQ stream protocol OAuth 2 support See Compatibility Notes below to learn about breaking or potentially breaking changes in this release. RabbitMQ releases are distributed via , , and . This release or later. This introduces feature parity for x86- and ARM64-based CPUs: Erlang 25 offers the JIT and tooling for both of those major CPU architectures. explains what package repositories and tools can be used to provision latest patch versions of Erlang 25.x. See the for documentation on upgrades and for release notes of other releases. RabbitMQ 3.11.0 before upgrading. If that is not the case, the upgrade process will not proceed. RabbitMQ 3.11.0 nodes can run alongside `3.10.x` nodes. `3.11.x`-specific features can only be made available when all nodes in the cluster upgrade to 3.11.0 or any other patch release in the series. While operating in mixed version mode, some aspects of the system may not behave as expected. The list of known behavior changes is covered below. Once all nodes are upgraded to 3.11.0, these irregularities will go away. Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended periods of time (no more than a few hours). RabbitMQ 3.11.0 will before upgrading. If the feature flags are not enabled, RabbitMQ 3.11 and later nodes will refuse to start. Starting with this release, RabbitMQ requires Erlang 25.0 or later versions. Nodes will fail to start on older Erlang releases. Erlang 25 as our new baseline means much improved performance on ARM64 architectures, across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. Nodes now default to 65536 concurrent client connections instead of using the effective kernel open file handle limit. Users who want to override this default, that is, have nodes that should support more concurrent connections and open files, now have to perform an additional configuration step: Pick a new limit value they would like to use, for instance, 100K Set the maximum open file handle limit (for example, via `systemd` or similar tooling) for the OS user used by RabbitMQ to 100K Set the to 100K This change was introduced because of a change in several Linux distributions: they now use a default open file handle limit so high, they cause a significant (say, 1.5 GiB) memory preallocated the Erlang runtime. For example, are examples of such distributions. The new default . See and for

Client libraries that were compatible with RabbitMQ `3.10.x` will be compatible with `3.11.0`. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . Release notes are kept under . Some features flags have . This means that they must be enabled before upgrading to 3.11. If that is not the case, the upgrade process will not proceed. More efficient connection tracking. This means less CPU load in environments where high cannot be avoided. In part contributed by @gomoripeti. GitHub issue: 10% to 20% throughput gain for publishers that use the default exchange. GitHub issue: When a virtual host is added, it now can be configured with default queue type. In part contributed by @adamncasey. GitHub issues: , Durable classic queues could get "lost" under certain conditions when a node failed. GitHub issue: Nodes could get stuck when performing a rolling restart on Kubernetes where DNS hostname resolution was not available early on node boot. For example, this is the case with a . GitHub issue: More robust free disk space monitoring implementation for Windows. GitHub issue: RabbitMQ now supports (super streams). Super streams are a way to scale out by partitioning a large stream into smaller streams. Stream protocol clients and RabbitMQ nodes now have a mechanism of exchanging their capabilities (sets of supported commands). GitHub issue: New stream protocol command that allows certain stream metadata to be inspected by applications. GitHub issue: . GitHub issue: Consumers now have access to their committed offset information. GitHub issue: OAuth 2 plugin now . GitHub issue: OAuth 2 plugin now supports . GitHub issue: Some counters on the Overview page have been moved to global counters introduced in RabbitMQ 3.9. GitHub issue: Management UI OAuth 2 integration supports more identity providers and . GitHub issue: HTTP API responses that render a large rest sets are now more efficient thanks to a more efficient JSON serialiser library used internally. Peak memory footprint of such queries is also double digit percent lower compared to v3.10.x. GitHub issue: New endpoints that can list and close connections of a specific user. Contributed by @NuwanSameera. GitHub issue: A way to configure an authentication timeout, much like in some other protocols RabbitMQ supports. Contributed by @gomoripeti. GitHub issue: A way to configure an authentication timeout, much like in some other protocols RabbitMQ supports. Contributed by @gomoripeti. GitHub issue: Dynamic Shovels that use the "on publish" mode now use flow control internally to avoid balooning Shovel memory usage when the publishing side outpaces its target node. Contributed by @gomoripeti. GitHub issue: `ra` upgraded to `osiris` upgraded to `prometheus` upgraded to `jsx` was replaced with To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.0.tar.xz` instead of the source tarball produced by GitHub.