rabbitmq/rabbitmq-server v3.8.12-rc.1

RabbitMQ 3.8.12-rc.1

on GitHub

RabbitMQ 3.8.12-rc.1

RabbitMQ 3.8.12-rc.1 is a preview of a maintenance release that contains bug fixes.

Erlang/OTP Compatibility Notes

This release requires Erlang 22 or
Erlang 23.

Provisioning Latest Erlang Releases explains
what package repositories and tools can be used to provision latest patch versions of Erlang 22.3.x.

Upgrade and Compatibility Notes

Upgrade Doc Guides and Change Log

See 3.8.0 release notes upgrade and
compatibility notes first if upgrading from an earlier release series (e.g. 3.7.x).

See the Upgrading guide for general documentation on upgrades and
RabbitMQ change log for release notes of other releases.

Upgrading to Erlang 22.x or Later Versions

When upgrading to this release from 3.7.15 or an older version, extra care has to be taken.

Because older RabbitMQ CLI tools can be incompatible with Erlang 22+ releases,
RabbitMQ must be upgraded at the same time as Erlang.

Alternatively the node can be upgraded to 3.7.18 on Erlang 21.3 first,
then Erlang 22.x or 23.x, then RabbitMQ to the most recent 3.8.x release.

Getting Help

Any questions about this release, upgrades or RabbitMQ in general are welcome on the RabbitMQ mailing list
and RabbitMQ community Slack.

Changes Worth Mentioning

Core Server

Bug Fixes

• Maintenance mode no longer transfers leaders of classic mirrored queue.

  The original transfer implementation was not guaranteed to be safe when only a
  subset of cluster nodes hosted replicas. In addition, the process could take
  a lot of time in environments with a lot of classic mirrored queues, more
  than in case of node shutdown.

  Quorum queue leadership transfer is still performed as it is dramatically more
  efficient and never suffered from any downsides of leadership transfer of CMQs.

  GitHub issue: #2749

• Default replica count for quorum queues was using an incorrect configuration key name.
  The default value is now 3, so in a cluster of five or seven nodes, only three
  will host replicas for newly declared quorum queues. One replica is the node to which
  the declaring client is connected to, two others are selected randomly.

  Declaring connections can control the number of replicas using the x-quorum-initial-group-size
  optional queue argument at declaration time.

  GitHub issue: #2759

• Memory monitor could run into an exception if queried very early on node boot
  before it was fully initialized.

  Contribute @tomyouyou.

  GitHub issue: #2733

Enhancements

• rabbitmq.conf validation of TLS certificate and private key paths is now more thorough:
  it checks if the files have read or read/write permissions instead of checking if it can read
  the file's metadata.

  GitHub issue: #2685

CLI Tools

Enhancements

• rabbitmqctl close_all_user_connections is a new command that closes all connections that
  authenticated using a specific username:

  rabbitmqctl close_all_user_connections "user-99fc15d3f" "closed to force reconnection"
  

  GitHub issue: #2715

Prometheus Plugin

Bug Fixes

• AuthN authentication attempts metrics produced duplicate TYPE and HELP strings in
  the scraping API endpoint output.

  Some metrics were renamed to avoid duplication. The new names are auth_attempts_detailed_total,
  auth_attempts_detailed_succeeded_total, and auth_attempts_detailed_failed_total.

  This issue is specific to RabbitMQ 3.8.10 and 3.8.11.

  GitHub issue: #2740

RabbitMQ Erlang Client

Bug Fixes

• The client performed hostname resolution twice even if IP version preference was specified by the user.

  Contributed by Pawel @haljin Antemijczuk.

  GitHub issue: #2748

Dependency Upgrades

• jose has been upgraded from 1.10.1 to 1.11.1

Source Code Archives

To obtain source code of the entire distribution, please download the archive named rabbitmq-server-3.8.12.tar.xz
instead of the source tarball produced by GitHub.