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

RabbitMQ `3.11.5` is a maintenance release in the `3.11.x` . Please refer to the upgrade section from if upgrading from a version prior to 3.11.0. This release requires Erlang 25. has more details on Erlang version requirements for RabbitMQ. As of 3.11.0, RabbitMQ requires Erlang 25. 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. Release notes can be found on GitHub at . Backported a number of improvements for non-ASCII character handling in paths on Windows. GitHub issue: Backported a number of free disk space monitor resiliency improvements. GitHub issue: If `handle.exe` is not available, free disk space monitor will now shell out to PowerShell to retrieve the number of open file handles used by the node. GitHub issue: `raft.adaptivefailuredetector.pollinterval` exposes 's `pollinterval` setting to RabbitMQ users. Increasing it can reduce the probability of false positives in clusters where inter-node communication links are used at close to maximum capacity. The default is `5000` (5 seconds). GitHub issue: When both `diskfreelimit.relative` and `diskfreelimit.absolute`, or both `vmmemoryhighwatermark.relative` and `vmmemoryhighwatermark.absolute` are set, the absolute settings will now take precedence. Contributed by @SimonUnge (AWS). GitHub issue: Closing channels will now log a warning if they had any messages pending a . Contributed by @Kiruamvp. GitHub issue: New quorum queue option for in-memory table (MemTable) compression. GitHub issue: Default queue type (a virtual host setting) is now applied when importing definitions into a single virtual host. GitHub issue: Feature flags provided by plugins were mistakingly disabled after node restart. GitHub issue: Classic queues with enabled could run into an exception. GitHub issue: When a was cleared, nodes emitted an of the wrong type. GitHub issue: `rabbitmq-queues grow` and `rabbitmq-queues shrink` misformatted the errors they could encounter. Contributed by @gomoripeti (CloudAMQP). GitHub issue: Implicit `help` command (when CLI tools were invoked without a command name) now respects all global flags (such as `--node`). For example, previously the `--node` flag in ``` shell rabbitmqctl --node rabbit@ns1.rabbitmq.cluster.local ``` was ignored but now CLI tools would discover what plugins are enabled on node `rabbit@ns1.rabbitmq.cluster.local` and include them into `help` output. GitHub issue: New key supported by `rabbitmqctl listqueues`: `effectivepolicy_definition` that returns merged definitions of regular and effective for the queue. GitHub issue: It is now possible to omit explicitly specifying queue type when declaring a queue (or stream) in the management UI, and rely on the default queue type configured for the selected virtual host. GitHub issue: New HTTP API endpoint, `GET /api/config/effective`, returns effective node configuration. This is an HTTP API counterpart of `rabbitmq-diagnostics environment`. Contributed by @SimonUnge (AWS). GitHub issue: Flow control state for Shovels is now reported with higher fidelity (of 1 second vs. several seconds previously). This means it should be easier to spot Shovels that run into flow control using management UI. Contributed by @gomoripeti (CloudAMQP). GitHub issue: Plugin could fail to boot and halt node boot due to incorrect boot step metadata. GitHub issue: `ra` was upgraded To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.5.tar.xz` instead of the source tarball produced by GitHub.