Skip to content

@pivotal-rabbitmq-ci pivotal-rabbitmq-ci released this Aug 4, 2020 · 727 commits to master since this release

RabbitMQ 3.8.6

RabbitMQ 3.8.6 is a maintenance release.
It focuses on bug fixes and usability improvements.

RabbitMQ Adopts the Mozilla Public License 2.0

Starting with this release, core RabbitMQ server and all tier 1 plugins
are relicensed under the Mozilla Public License 2.0
(previously used license: the Mozilla Public License 1.1).

The permissiveness of the MPL 2.0 is largely the same as of the MPL 1.1.
See the MPL 2.0 FAQ and
MPL 2.0 Revision and Changes FAQ to learn more.

Erlang 23 Compatibility

This release is compatible with Erlang 23.

Erlang/OTP Compatibility Notes

This release requires Erlang/OTP 21.3 or later.
22.3 or 23.0 releases are recommended.

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

Deprecations

This release removed HiPE precompilation support. HiPE has been deprecated and
mostly unmaintained since Erlang 22, and will be replaced with a JIT in Erlang 24
in 2021.

rabbitmqctl hipe_compile

and

hipe_compile = true

are both retained for backwards compatibility but they won't have any effect.

Upgrade Doc Guides and Change Log

See 3.8.0 release notes upgrade and
compatibility notes first if upgrading from an earlier release.

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

Upgrading to Erlang 21.x or Later Versions

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 22.x or 23.x, then RabbitMQ to 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.

Changes Worth Mentioning

Core Server

License Change

RabbitMQ has been relicensed under the Mozilla Public License 2.0
(previously used license: the Mozilla Public License 1.1).

The permissiveness of the MPL 2.0 is largely the same as of the MPL 1.1.
See the MPL 2.0 FAQ and
MPL 2.0 Revision and Changes FAQ to learn more.

Deprecations

Bug Fixes

  • Definition import on node boot (via the load_definitions configuration setting) is now performed
    after plugins are enabled.

    This resolves a long standing chicken-and-egg dependency problem that prevented definitions
    that depend on plugins being functional from being successfully imported during node boot.

    Some affected features include

    GitHub issue: rabbitmq/rabbitmq-server#2384

  • Similarly, client connection listeners (both TCP and TLS-enabled) are now started after
    plugin activation. This makes certain configurations that use the trust store plugin
    behave as expected.

    GitHub issue: rabbitmq/rabbitmq-server#2405

  • Environment variables prefixed with RABBITMQ_ were ignored when used in the rabbitmq-env.conf file,
    while their prefixless counterparts worked as expected.

    GitHub issue: rabbitmq/rabbitmq-common#401

Enhancements

CLI Tools

Deprecations

Bug Fixes

Enhancements

  • rabbitmq-queues check_if_node_is_quorum_critical and rabbitmq-queues check_if_node_is_mirror_sync_critical checks
    have been adjusted. They now special case single node clusters as the check does not make much sense
    in those environments.

    rabbitmq-queues check_if_node_is_mirror_sync_critical now also excludes exclusive queues from
    consideration as they, even if matched by a policy that enables classic queue mirroring,
    would not actually be mirrored.

    GitHub issue: rabbitmq/rabbitmq-cli#432

  • rabbitmq-diagnostics status now includes the total amount of memory used by the node in its
    regular output. It was previously only available when --formatter=json switch was used.

    GitHub issue: rabbitmq/rabbitmq-cli#449

  • rabbitmq-diagnostics erlang_cookie_sources is a new command that helps with troubleshooting
    CLI tool authentication to nodes by listing relevant environment information about the
    shared secret. The actual secret
    is not displayed for obvious security reasons.

    GitHub issue: rabbitmq/rabbitmq-cli#446

  • rabbitmqct eval_file is a new command that evaluates Erlang code expressions from a local file
    on the target node:

    rabbitmqctl eval_file /path/to/code_snippet.escript

    GitHub issue: rabbitmq/rabbitmq-cli#438

  • rabbitmqct eval now accepts code snippets from standard input:

    rabbitmqctl eval <<EOF
     io:format("~p~n", [
         rabbit:product_info()
     ]).
    rabbitmqctl eval < code_snippet.escript

    GitHub issue: rabbitmq/rabbitmq-cli#438

  • rabbitmq-diagnostics resolve_hostname is a new command that resolves a hostname either locally
    or on the node, and returns the resolved IPv4 or IPv6 addresses.

    The command can help quickly detect hostname resolution irregularities on a node, including
    the effects of Erlang inetrc file settings.
    Hostname resolution issues can cause CLI tools, cluster formation and peer reconnection to
    not work as expected.

    Some examples:

    rabbitmq-diagnostics resolve_hostname "google.com" --address-family ipv4
    
    rabbitmq-diagnostics resolve_hostname "google.com" --address-family ipv6 --offline

    GitHub issue: rabbitmq/rabbitmq-cli#431

  • All CLI tools now provide an autocomplete [prefix] command that lists command completion
    options. It is intended to be used to implement autocompletion of command names in shells.

    GitHub issue: rabbitmq/rabbitmq-cli#439

Management Plugin

Bug Fixes

Enhancements

Federation Plugin

Bug Fixes

  • In environments where rabbitmq_federation.pgroup_name_cluster_id is not set or set to undefined,
    links will treat such values as a false (the default) instead of failing with an exception.

    GitHub issue: rabbitmq/rabbitmq-federation#109

MQTT Plugin

Bug Fixes

  • The plugin could fail to accept new client connections with an exception in some cases.

    GitHub issue: rabbitmq/rabbitmq-mqtt#235

Web STOMP Plugin

Enhancements

Web MQTT Plugin

Enhancements

AuthN/AuthZ Backend HTTP Plugin

Bug Fixes

Dependency Upgrades

Source code archives

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.6.tar.xz.

Assets 42
Jul 29, 2020
Release 3.8.6-rc.2
Pre-release
Pre-release

@pivotal-rabbitmq-ci pivotal-rabbitmq-ci released this Jul 28, 2020 · 727 commits to master since this release

RabbitMQ 3.8.6-rc.1

RabbitMQ 3.8.6-rc.1 is a preview of a maintenance release.
It focuses on bug fixes and usability improvements.

RabbitMQ Adopts the Mozilla Public License 2.0

Starting with this release, core RabbitMQ server and all tier 1 plugins
are relicensed under the Mozilla Public License 2.0
(previously used license: the Mozilla Public License 1.1).

The permissiveness of the MPL 2.0 is largely the same as of the MPL 1.1.
See the MPL 2.0 FAQ and
MPL 2.0 Revision and Changes FAQ to learn more.

Erlang 23 Compatibility

This release is compatible with Erlang 23.

Erlang/OTP Compatibility Notes

This release requires Erlang/OTP 21.3 or later.
22.3 or 23.0 releases are recommended.

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

Deprecations

This release removed HiPE precompilation support. HiPE has been deprecated and
mostly unmaintained since Erlang 22, and will be replaced with a JIT in Erlang 24
in 2021.

rabbitmqctl hipe_compile

and

hipe_compile = true

are both retained for backwards compatibility but they won't have any effect.

Upgrade Doc Guides and Change Log

See 3.8.0 release notes upgrade and
compatibility notes first if upgrading from an earlier release.

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

Upgrading to Erlang 21.x or Later Versions

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 22.x or 23.x, then RabbitMQ to 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.

Changes Worth Mentioning

Core Server

License Change

RabbitMQ has been relicensed under the Mozilla Public License 2.0
(previously used license: the Mozilla Public License 1.1).

The permissiveness of the MPL 2.0 is largely the same as of the MPL 1.1.
See the MPL 2.0 FAQ and
MPL 2.0 Revision and Changes FAQ to learn more.

Deprecations

Bug Fixes

  • Definition import on node boot (via load_definitions configuration setting) is now performed
    after plugins are enabled.

    This resolves a long standing chicken-and-egg dependency problem that prevented definitions
    that depend on plugins being functional from being successfully imported during node boot.

    Some affected features include

    GitHub issue: rabbitmq/rabbitmq-server#2384

  • Similarly, client connection listeners (both TCP and TLS-enabled) are now started after
    plugin activation. This makes certain configurations that use the trust store plugin
    behave as expected.

    GitHub issue: rabbitmq/rabbitmq-server#2405

  • Environment variables prefixed with RABBITMQ_ were ignored when used in the rabbitmq-env.conf file,
    while their prefixless counterparts worked as expected.

    GitHub issue: rabbitmq/rabbitmq-common#401

Enhancements

CLI Tools

Deprecations

Bug Fixes

Enhancements

  • rabbitmq-queues check_if_node_is_quorum_critical and rabbitmq-queues check_if_node_is_mirror_sync_critical checks
    have been adjusted. They now special case single node clusters as the check does not make much sense
    in those environments.

    rabbitmq-queues check_if_node_is_mirror_sync_critical now also excludes exclusive queues from
    consideration as they, even if matched by a policy that enables classic queue mirroring,
    would not actually be mirrored.

    GitHub issue: rabbitmq/rabbitmq-cli#432

  • rabbitmq-diagnostics erlang_cookie_sources is a new command that helps with troubleshooting
    CLI tool authentication to nodes by listing relevant environment information about the
    shared secret. The actual secret
    is not displayed for obvious security reasons.

    GitHub issue: rabbitmq/rabbitmq-cli#446

  • rabbitmqct eval_file is a new command that evaluates Erlang code expressions from a local file
    on the target node:

    rabbitmqctl eval_file /path/to/code_snippet.escript

    GitHub issue: rabbitmq/rabbitmq-cli#438

  • rabbitmqct eval now accepts code snippets from standard input:

    rabbitmqctl eval <<EOF
     io:format("~p~n", [
         rabbit:product_info()
     ]).
    rabbitmqctl eval < code_snippet.escript

    GitHub issue: rabbitmq/rabbitmq-cli#438

  • rabbitmq-diagnostics resolve_hostname is a new command that resolves a hostname either locally
    or on the node, and returns the resolved IPv4 or IPv6 addresses.

    The command can help quickly detect hostname resolution irregularities on a node, including
    the effects of Erlang inetrc file settings.
    Hostname resolution issues can cause CLI tools, cluster formation and peer reconnection to
    not work as expected.

    Some examples:

    rabbitmq-diagnostics resolve_hostname "google.com" --address-family ipv4
    
    rabbitmq-diagnostics resolve_hostname "google.com" --address-family ipv6 --offline

    GitHub issue: rabbitmq/rabbitmq-cli#431

  • All CLI tools now provide an autocomplete [prefix] command that lists command completion
    options. It is intended to be used to implement autocompletion of command names in shells.

    GitHub issue: rabbitmq/rabbitmq-cli#439

Management Plugin

Bug Fixes

Enhancements

Federation Plugin

Bug Fixes

  • In environments where rabbitmq_federation.pgroup_name_cluster_id is not set or set to undefined,
    links will treat such values as a false (the default) instead of failing with an exception.

    GitHub issue: rabbitmq/rabbitmq-federation#109

MQTT Plugin

Bug Fixes

  • The plugin could fail to accept new client connections with an exception in some cases.

    GitHub issue: rabbitmq/rabbitmq-mqtt#235

Web STOMP Plugin

Enhancements

Web MQTT Plugin

Enhancements

AuthN/AuthZ Backend HTTP Plugin

Bug Fixes

Dependency Upgrades

Source code archives

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.6.tar.xz.

Assets 42
Jul 27, 2020
Release 3.8.6-beta.1

@pivotal-rabbitmq-ci pivotal-rabbitmq-ci released this Jul 24, 2020 · 1866 commits to master since this release

RabbitMQ 3.7.27

RabbitMQ 3.7.27 is a maintenance release. It contains a couple of backports
from the 3.8.x branch.

RabbitMQ 3.7.x series are out of general support and covered by the limited extended support policy only.

Please consider upgrading to RabbitMQ 3.8.x.

Erlang/OTP Compatibility Notes

This release no longer supports Erlang/OTP 20.3.
Erlang 21.3+ is now a hard requirement checked on node startup.

Make sure a supported Erlang version is used before upgrading.
Provisioning Latest Erlang Releases explains
what package repositories and tools can be used to provision latest patch versions of Erlang 21.3.x and 22.x.

Compatibility Notes

Upgrading to Erlang 21.x or Later Versions

When upgrading to this release and upgrading Erlang to 21.x or later at the same time, 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 before Erlang.

Upgrade Doc Guides and Change Log

See 3.7.0 release notes upgrade
and compatibility notes first if upgrading from an earlier release.

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

Getting Help

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

Changes

Core Server

Enhancements

  • More peer discovery errors are retried.

    GitHub issue: rabbitmq/rabbitmq-server#1627

  • Initial Erlang/OTP 24 compatibility.

    Erlang/OTP 24 is expected to ship in mid-2021. While RabbitMQ 3.7 will be out of support by then,
    some initial compatibility work was backported to this branch due to contious integration on Erlang/OTP master.

Federation Plugin

Bug Fixes

  • One-off connections periodically used by exchange federation links now handle timeouts in certain
    operations gracefully. This avoids unnecessary link disruption and restarts in certain environments.
    The default interval has also been bumped from 30s to 90s.

    In environments with stable topologies the interval can be significantly increased to decrease connection
    churn, simplify monitoring and in general conserve some resources:

    %% advanced.config
    [
     {rabbitmq_federation, [
         %% 86400 seconds or 24 hours
         {internal_exchange_check_interval, 86400000}
     ]}
    ].

    GitHub issue: rabbitmq/rabbitmq-federation#107

Source code archives

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.7.27.tar.xz.

Assets 42
Jul 24, 2020
Release 3.7.27-rc.2
Pre-release
Pre-release

@pivotal-rabbitmq-ci pivotal-rabbitmq-ci released this Jun 25, 2020 · 1866 commits to master since this release

RabbitMQ 3.7.27-rc.1

RabbitMQ 3.7.27-rc.1 is a preview of a maintenance release. It focuses on bug fixes.

RabbitMQ 3.7.x series are out of general support and covered by the limited extended support policy.

Please consider upgrading to RabbitMQ 3.8.x.

Erlang/OTP Compatibility Notes

This release no longer supports Erlang/OTP 20.3.
Erlang 21.3+ is now a hard requirement checked on node startup.

Make sure a supported Erlang version is used before upgrading.
Provisioning Latest Erlang Releases explains
what package repositories and tools can be used to provision latest patch versions of Erlang 21.3.x and 22.x.

Compatibility Notes

Upgrading to Erlang 21.x or Later Versions

When upgrading to this release and upgrading Erlang to 21.x or later at the same time, 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 before Erlang.

Upgrade Doc Guides and Change Log

See 3.7.0 release notes upgrade
and compatibility notes first if upgrading from an earlier release.

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

Getting Help

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

Changes

Federation Plugin

Bug Fixes

  • One-off connections periodically used by exchange federation links now handle timeouts in certain
    operations gracefully. This avoids unnecessary link disruption and restarts in certain environments.
    The default interval has also been bumped from 30s to 90s.

    In environments with stable topologies the interval can be significantly increased to decrease connection
    churn, simplify monitoring and in general conserve some resources:

    %% advanced.config
    [
     {rabbitmq_federation, [
         %% 86400 seconds or 24 hours
         {internal_exchange_check_interval, 86400000}
     ]}
    ].

    GitHub issue: rabbitmq/rabbitmq-federation#107

Source code archives

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.7.27.tar.xz.

Assets 42

@pivotal-rabbitmq-ci pivotal-rabbitmq-ci released this Jun 15, 2020 · 727 commits to master since this release

RabbitMQ 3.8.5

RabbitMQ 3.8.5 is a maintenance release.
It focuses on bug fixes and usability improvements.

This release is compatible with Erlang 23.

Erlang/OTP Compatibility Notes

This release requires Erlang/OTP 21.3 or later.
22.3 or 23.0 releases are recommended.

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

Deprecations

This release deprecates rabbitmq-diagnostics node_health_check (née rabbitmqctl node_health_check).
See the section on CLI tools changes below to learn more.

Upgrade Doc Guides and Change Log

See 3.8.0 release notes upgrade and
compatibility notes first if upgrading from an earlier release.

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

Upgrading to Erlang 21.x or Later Versions

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 22.x or 23.x, then RabbitMQ to 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.

Changes Worth Mentioning

Core Server

Bug Fixes

Enhancements

  • Raft data directory now can be configured using ra.data_dir configuration key:

    ra.data_dir = /path/to/raft/data/directory

    GitHub issue: rabbitmq/rabbitmq-server#2354

  • User and permission management operations now produce clear log entries when they succeed,
    not just when they fail. This helps auditing in environments that have stricter security and audit
    requirements.

    GitHub issue: rabbitmq/rabbitmq-server#2363

CLI Tools

Bug Fixes

Deprecations

  • rabbitmq-diagnostics node_health_check (née rabbitmqctl node_health_check) is deprecated and will be
    removed in a future version.

    node_health_check (as well as its HTTP API counterpart) is an opinionated, intrusive, aspirational attempt
    at producing One True Health Check™ for RabbitMQ that was envisioned and added to CLI tools around 2015-2016.

    It has proven to be too prone to false positives, can consume a prohibitive
    amount of CPU and runtime scheduler resources, and tends to be too opinionated
    for many technical operations teams.

    A much more modular, pick-and-choose approach has been adopted since
    but this command has never been deprecated. Until now.

    GitHub issue: rabbitmq/rabbitmq-cli#426

Management Plugin

Bug Fixes

Consistent Hashing Exchange

Bug Fixes

  • Due to later plugin activation in 3.8.4, durable
    consistent hashing exchanges were skipped during topology recovery. In practice that meant these exchanges
    did not route messages published to it.

    Now the plugin reconstructs consistent hashing ring manually for every durable exchange of this type and
    routing functions as expected.

    Kudos to Rob Gerritsen and Raimond @rai69 Kuipers for helping with discovery of this issue.

    GitHub issue: rabbitmq/rabbitmq-consistent-hash-exchange#45

Enhancements

  • rabbitmq-diagnostics consistent_hash_exchange_ring_state <exchange> is a new CLI command that makes it
    easy to inspect consistent hashing ring state for an exchange.

    GitHub issue: rabbitmq/rabbitmq-consistent-hash-exchange#47

MQTT Plugin

Bug Fixes

Web STOMP Plugin

Enhacenements

AWS Peer Discovery Plugin

Enhancements

  • AWS peer discovery backend can be specified as aws:

    cluster_formation.peer_discovery_backend = aws

    as well as the module name, or plugin name (rabbitmq_peer_discovery_aws):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_aws

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-aws#34

Consul Peer Discovery Plugin

Enhancements

  • Consul peer discovery backend can be specified as consul:

    cluster_formation.peer_discovery_backend = consul

    as well as the module name, or plugin name (rabbitmq_peer_discovery_consul):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_consul

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-consul#43

etcd Peer Discovery Plugin

Bug Fixes

Enhancements

  • etcd peer discovery backend can be specified as etcd:

    cluster_formation.peer_discovery_backend = etcd

    as well as the module name, or plugin name (rabbitmq_peer_discovery_etcd):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_etcd

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-etcd#26

Kubernetes Peer Discovery Plugin

Enhancements

  • Kubernetes peer discovery backend can be specified as k8s or kubernetes:

    cluster_formation.peer_discovery_backend = k8s

    as well as the module name, or plugin name (rabbitmq_peer_discovery_k8s):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_k8s

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-k8s#65

Web STOMP Plugin

Enhancements

Debian Package

Enhancements

RPM Package

Enhancements

Dependency Upgrades

Source code archives

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.5.tar.xz.

Assets 42
Pre-release
Pre-release

@pivotal-rabbitmq-ci pivotal-rabbitmq-ci released this Jun 14, 2020 · 727 commits to master since this release

RabbitMQ 3.8.5-rc.2

RabbitMQ 3.8.5-rc.2 is a maintenance release candidate.
It focuses on bug fixes and usability improvements.

This release is compatible with Erlang 23.

Erlang/OTP Compatibility Notes

This release requires Erlang/OTP 21.3 or later.
22.3 or 23.0 releases are recommended.

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

Deprecations

This release deprecates rabbitmq-diagnostics node_health_check (née rabbitmqctl node_health_check).
See the section on CLI tools changes below to learn more.

Upgrade Doc Guides and Change Log

See 3.8.0 release notes upgrade and
compatibility notes first if upgrading from an earlier release.

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

Upgrading to Erlang 21.x or Later Versions

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 22.x or 23.x, then RabbitMQ to 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.

Changes Worth Mentioning

Core Server

Bug Fixes

Enhancements

  • Raft data directory now can be configured using ra.data_dir configuration key:

    ra.data_dir = /path/to/raft/data/directory

    GitHub issue: rabbitmq/rabbitmq-server#2354

  • User and permission management operations now produce clear log entries when they succeed,
    not just when they fail. This helps auditing in environments that have stricter security and audit
    requirements.

    GitHub issue: rabbitmq/rabbitmq-server#2363

CLI Tools

Bug Fixes

Deprecations

  • rabbitmq-diagnostics node_health_check (née rabbitmqctl node_health_check) is deprecated and will be
    removed in a future version.

    node_health_check (as well as its HTTP API counterpart) is an opinionated, intrusive, aspirational attempt
    at producing One True Health Check™ for RabbitMQ that was envisioned and added to CLI tools around 2015-2016.

    It has proven to be too prone to false positives, can consume a prohibitive
    amount of CPU and runtime scheduler resources, and tends to be too opinionated
    for many technical operations teams.

    A much more modular, pick-and-choose approach has been adopted since
    but this command has never been deprecated. Until now.

    GitHub issue: rabbitmq/rabbitmq-cli#426

Management Plugin

Bug Fixes

Consistent Hashing Exchange

Bug Fixes

  • Due to later plugin activation in 3.8.4, durable
    consistent hashing exchanges were skipped during topology recovery. In practice that meant these exchanges
    did not route messages published to it.

    Now the plugin reconstructs consistent hashing ring manually for every durable exchange of this type and
    routing functions as expected.

    Kudos to Rob Gerritsen and Raimond @rai69 Kuipers for helping with discovery of this issue.

    GitHub issue: rabbitmq/rabbitmq-consistent-hash-exchange#45

Enhancements

  • rabbitmq-diagnostics consistent_hash_exchange_ring_state <exchange> is a new CLI command that makes it
    easy to inspect consistent hashing ring state for an exchange.

    GitHub issue: rabbitmq/rabbitmq-consistent-hash-exchange#47

MQTT Plugin

Bug Fixes

Web STOMP Plugin

Enhacenements

AWS Peer Discovery Plugin

Enhancements

  • AWS peer discovery backend can be specified as aws:

    cluster_formation.peer_discovery_backend = aws

    as well as the module name, or plugin name (rabbitmq_peer_discovery_aws):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_aws

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-aws#34

Consul Peer Discovery Plugin

Enhancements

  • Consul peer discovery backend can be specified as consul:

    cluster_formation.peer_discovery_backend = consul

    as well as the module name, or plugin name (rabbitmq_peer_discovery_consul):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_consul

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-consul#43

etcd Peer Discovery Plugin

Bug Fixes

Enhancements

  • etcd peer discovery backend can be specified as etcd:

    cluster_formation.peer_discovery_backend = etcd

    as well as the module name, or plugin name (rabbitmq_peer_discovery_etcd):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_etcd

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-etcd#26

Kubernetes Peer Discovery Plugin

Enhancements

  • Kubernetes peer discovery backend can be specified as k8s or kubernetes:

    cluster_formation.peer_discovery_backend = k8s

    as well as the module name, or plugin name (rabbitmq_peer_discovery_k8s):

    cluster_formation.peer_discovery_backend = rabbit_peer_discovery_k8s

    GitHub issue: rabbitmq/rabbitmq-peer-discovery-k8s#65

Web STOMP Plugin

Enhancements

Debian Package

Enhancements

RPM Package

Enhancements

Dependency Upgrades

Source code archives

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.5.tar.xz.

Assets 42
Jun 11, 2020
Release 3.8.5-rc.1
You can’t perform that action at this time.