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

RabbitMQ `3.8.3` is a maintenance release. This release or later. `22.x` series is recommended. explains what package repositories and tools can be used to provision latest patch versions of Erlang `21.3.x` and `22.x`. When upgrading to this release from `3.7.6` or an older version, extra care has to be taken. Since CLI tools from RabbitMQ releases older than 3.7.7 will fail on Erlang 21 or later, RabbitMQ must be upgraded at the same time as Erlang. Alternatively the node can be upgraded to `3.7.18` first, then Erlang 21.x or 22.x, then to RabbitMQ 3.8.x. See upgrade and compatibility notes first if upgrading from an earlier release. See the for general documentation on upgrades and for release notes of other releases. Any questions about this release, upgrades or RabbitMQ in general are welcome on the . Reduced scheduled GC activity in connection socket writer to one run per 1 GiB of data transferred, with an option to change the value or disable scheduled run entirely. More frequent binary heap GC runs seem unneccesary on Erlang 22. Contributed by Aleksander Nycz. GitHub issue: Eliminated an inefficiency in recovery of quorum queues with a backlog of messages. GitHub issue: In a case where a node hosting a quorum queue replica went offline and was removed from the cluster, and later came back, quorum queues could enter a loop of Raft leader elections. GitHub issue: Quorum queues with a dead lettering could fail to recover. GitHub issue: The node now can recover even if virtual host recovery terms file was corrupted. Contributed by @tomyouyou. GitHub issue: Autoheal could fail to finish if one of its state transitions initiated by a remote node timed out. Contributed by @tomyouyou. GitHub issue: Syslog client is now started even when Syslog logging is configured only for some log sinks. GitHub issue: Policies that quorum queues ignored were still listed as applied to them. GitHub issue: If a quorum queue leader rebalancing operation timed out, CLI tools failed with an exception instead of a sensible internal API response. Contributed by Gabriele Santomaggio. GitHub issue: Handle timeout error on the rebalance function. Contributed by Gabriele Santomaggio. GitHub issue: Handle and raise protocol error for absent queues assumed to be alive. Contributed by Ayanda Dube. GitHub issue: Some Proxy protocol errors are now logged at debug level. This reduces log noise in environments where TCP load balancers and proxies perform health checks by opening a TCP connection but never sending any data. GitHub issue: Quorum queue deletion operation no longer supports the "if unused" and "if empty" options. They are typically used for transient queues don't make much sense for quorum ones. GitHub issue: Do not treat applications that do not depend on rabbit as plugins. This is especially important for applications that should not be stopped before rabbit is stopped. GitHub Issue: RabbitMQ nodes will now gracefully shutdown when receiving a `SIGTERM`

Previously the runtime would invoke a default handler that terminates the VM giving RabbitMQ no chance to execute its shutdown steps. GitHub issue: Every cluster now features a persistent internal cluster ID that can be used by core features or plugins. Unlike the human-readable cluster name, the value cannot be overridden by the user. GitHub issue: Speedup execution of boot steps by a factor of 2N, where N is the number of attributes per step. Contributed by Ayanda Dube. GitHub issue: `rabbitmq-diagnostics status` failed to display the results when executed against a node that had high VM watermark set as an absolute value (using `vmmemoryhigh_watermark.absolute`). GitHub issue: New health checks that can be used to determine if it's a good moment to shut down a node for an upgrade. ``` sh rabbitmq-diagnostics checkifnodeismirrorsynccritical rabbitmq-diagnostics checkifnodeisquorum_critical ``` GitHub issue: Some proxy protocol errors are now logged at debug level. This reduces log noise in environments where TCP load balancers and proxies perform health checks by opening a TCP connection but never sending any data. GitHub issue: Consumer section on individual page was unintentionally hidden. GitHub issue: Fix queue-type select by adding unsafe-inline CSP policy. GitHub issue: An undocumented "automagic login" feature on the login form was removed. GitHub issue: A new `POST /login` endpoint can be used by custom management UI login forms to authenticate the user and set the cookie. GitHub issue: A new `POST /rebalance/queues` endpoint that is the HTTP API equivalent of `rabbitmq-queues rebalance` GitHub issue: Warning about a missing `handle.exe` in `PATH` on Windows is now only logged every 10 minutes. GitHub issue: `rabbitmqadmin declare queue` now supports a new `queue_type` parameter to simplify declaration of quorum queues. GitHub issue: HTTP API request log entries now includes acting user. GitHub issue: are now also set for static assets such as JavaScript files. GitHub issue: Add option to aggregate metrics for channels, queues & connections. Metrics are now aggregated by default (safe by default). This new behaviour can be disabled via `prometheus.returnperobject_metrics = true` config. GitHub issue: The plugin will now notify of node startup and peer stop/unavailability events. Contributed by Gabriele Santomaggio. GitHub issue: Only run healthcheck when backend is configured. GitHub issue: Use vhost to delete federated exchange. . GitHub issue: "Command" operations such as binding propagation now use a separate channel for all links, preventing latency spikes for asynchronous operations (such as message publishing) (a head-of-line blocking problem). Contributed by Grigory Starinkin. GitHub issue: Additional scopes can be fetched from a predefined JWT token field. Those scopes will be combined with the standard scopes field. Contributed by @papugamichal. GitHub issue: HTTPS certificate provider will not longer terminate if upstream service response contains invalid JSON. GitHub issue: Avoid blocking when registering or unregistering a client ID. GitHub issue: Handle heartbeat in `close_sent/2`. GitHub issue: Warning: The source code archive provided by GitHub only contains the source of the broker, not the plugins or the client libraries. Please download the archive named `rabbitmq-server-3.8.3.tar.xz`. observer-cli was upgraded prometheus.erl was upgraded ra was upgraded