release-notes/3.13.4.md
RabbitMQ 3.13.4 is a maintenance release in the 3.13.x release series.
Please skip this release and upgrade straight to 3.13.6 or a later version (if available).
Starting June 1st, 2024, community support for this series will only be provided to regularly contributing users and those who hold a valid commercial support license.
Please refer to the upgrade section from the 3.13.0 release notes if upgrading from a version prior to 3.13.0.
This release requires Erlang 26 and supports Erlang versions up to 26.2.x.
RabbitMQ and Erlang/OTP Compatibility Matrix has more details on
Erlang version requirements for RabbitMQ.
As of 3.13.0, RabbitMQ requires Erlang 26. Nodes will fail to start on older Erlang releases.
Users upgrading from 3.12.x (or older releases) on Erlang 25 to 3.13.x on Erlang 26 (both RabbitMQ and Erlang are upgraded at the same time) must consult the v3.12.0 release notes and v3.13.0 release notes first.
Release notes can be found on GitHub at rabbitmq-server/release-notes.
A rolling upgrade from 3.12.14 to 3.13.x could run into an exception.
GitHub issue: #11380
When an existing virtual host was re-imported from a definitions file, its default queue type (DQT) was cleared (reset) if that field was missing in the imported definitions.
Now the existing DQT is preserved.
GitHub issue: #11457
When a queue was declared without an explicitly provided x-queue-type but a default
queue type (DQT) set (for its virtual host), its redeclaration did not consider
the DQT during the property equivalence check stage.
GitHub issue: #11541
Feature flag controller could run into a deadlock in some upgrade scenarios.
GitHub issue: #11414
In mixed 3.13.x and 3.12.x clusters, when a Direct Reply-to client (the app that initiates requests)
was connected to the 3.13 node and the server (the app that responds) was connected to the 3.12 node,
the response was lost due to a message format conversion exception.
GitHub issue: #11401
In some parallel cluster formation scenarios where definitions were imported on node boot, the virtual hosts created by the import can only be started on a subset of nodes. This is so because not all cluster peers are known at virtual host creation time.
To reconcile (repair) this state, nodes will periodically check that all virtual hosts are initialized on all cluster nodes. This happens every thirty seconds for the first five minutes since node boot. As long as the cluster is fully formed within that amount of time, all nodes will have performed initialization for all virtual hosts that exist.
GitHub issue: #11408
Quorum queue leader replicas now initiate reconciliation (repair) of their replicas, if there are any missing, more frequently, making quorum queues more defensive in the case of (highly discouraged) grow-then-shrink upgrades.
As part of this change, the CPU cost of reconciliation was reduced, now accounting for less than 1% of the CPU with 10K quorum queues in some test environments.
Contributed by @SimonUnge.
GitHub issue: #11029
In the case where the vhost_max node limit is reached, the node will log specific errors
when a new virtual host is (unsuccessfully) added.
Contributed by @SimonUnge.
GitHub issue: #11589
Elapsed time in the logs is now measured using monotonic time.
GitHub issue: #11396
rabbitmq-diagnostics check_if_node_is_quorum_critical could report a false positive
when some quorum queue replcas where very recently added or very recently restarted.
GitHub issue: #11524
rabbitmqctl list_unresponsive_queues ran into an exception if there were connected MQTT clients
with QoS 0 subscriptions.
Partially contributed by @gomoripeti.
GitHub issue: #11434
CLI tools now can be built with Elixir 1.17.x.
Contributed by @VlkrS.
GitHub issue: #11529
OpenID Connect discovery endpoint now can be overridden for identity providers with non-standard configurations.
GitHub issue: #11103
Virtual host metadata was not included into definition files exported via the HTTP API.
GitHub issue: #10515
When Khepri was enabled and a majority of cluster members were down, adding a virtual host failed with an unhelpful exception.
GitHub issue: #11590
When default queue type is set on a virtual host but not for individual queues,
the exported queues will have x-queue-type set to the default type in the
exported definitions document.
GitHub issue: #10515
Management UI will now display the number of cores available to the node.
GitHub issue: #11382
OAuth 2-specific JavaScript files are now only loaded if the OAuth 2 plugin is enabled on the node.
GitHub issue: #11421
TLS-related settings, in particular related to peer certificate chain verification, now can be configured for this plugin:
auth_http.ssl_options.verify = verify_none
auth_http.ssl_options.fail_if_no_peer_cert = false
Please remember that disabling peer certificate chain verification makes the system less secure and susceptible to Man-in-the-Middle attacks. Consider enabling the verification in production systems when possible.
GitHub issue: #10281
The plugin failed to extract discovered nodes name correctly in earlier 3.13.x
releases.
GitHub issue: #11445
tracing.dir, tracing.username and tracing.password are the three Tracing plugin
settings that can be set via rabbitmq.conf.
GitHub issue: #11554
2.11.01.8.21.11.10To obtain source code of the entire distribution, please download the archive named rabbitmq-server-3.13.4.tar.xz
instead of the source tarball produced by GitHub.