RabbitMQ 3.6.13 RC2

RabbitMQ 3.6.13 RC2

RabbitMQ 3.6.13 RC2 is a maintenance release candidate.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.12.
See the upgrade and compatibility sections in the 3.6.7 release notes if upgrading from an earlier release.

Core Server

Bug Fixes

• Memory usage monitor uses subprocesses a lot more sparingly. They are started
  roughly once a second or not started at all, depending on the strategy (e.g. on Windows
  Erlang VM allocator information is used instead).

  GitHub issues: rabbitmq-server#1343, rabbitmq-common#224

• Very busy queues are now more efficient at prioritizing consumers, avoiding
  consumer delivery blocking when relatively long running operations (e.g. bulk flushing
  of transient messages to disk) happen.

  GitHub issues: rabbitmq-server#1388, rabbitmq-server#1407

• Queue master strategies now take additional queue HA arguments into account.

  GitHub issue: rabbitmq-server#1371

• Logging to standard output using RABBITMQ_LOGS=- wasn't possible on Windows.

  GitHub issue:

• Queue master locator name now can be specified as Erlang strings.

  GitHub issue: rabbitmq-server#1411

• Direct Erlang client connections could fail with obscure messages when
  target node was still booting.

  GitHub issue: rabbitmq-server#1356

Enhancements

• supervisor2 now can be used in environments that perform hot code upgrades.

  GitHub issue: rabbitmq-common#230

• systemd service file now white lists exit code 69.

  GitHub issue: rabbitmq-server-release#51

• Example systemd service file now includes service restart settings.

  GitHub issue: rabbitmq-server#1359

• Queue master locator strategy now can be configured using strings.

  GitHub issue: rabbitmq-server#1411

• Plugin activation avoids logs things that can be confusing.

  GitHub issue: rabbitmq-server#1364

Management Plugin

Enhancements

• Minor efficiency improvements around stats collection.

  GitHub issues: rabbitmq-common#235

• jQuery upgraded to 1.12.4.

  GitHub issue: rabbitmq-management#502

• UI improvements.

• It is now possible to configure an HTTP API path prefix for the plugin.

  GitHub issue: rabbitmq-management#481

• Queue details page no longer truncates node name.

  GitHub issue: rabbitmq-management#473

• Policy name in queue and exchange info is now a link.

  GitHub issue: rabbitmq-management#493

• DELETE /api/connections/{name} is now more defensive.

  GitHub issue: rabbitmq-management#497

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

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-3.6.13.tar.gz.

RabbitMQ 3.6.13 RC1

RabbitMQ 3.6.13 RC1

RabbitMQ 3.6.13 RC1 is a maintenance release candidate.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.12.
See the upgrade and compatibility sections in the 3.6.7 release notes if upgrading from an earlier release.

Core Server

Bug Fixes

• Memory usage monitor uses subprocesses a lot more sparingly. They are started
  roughly once a second or not started at all, depending on the strategy (e.g. on Windows
  Erlang VM allocator information is used instead).

  GitHub issues: rabbitmq-server#1343, rabbitmq-common#224

• Very busy queues are now more efficient at prioritizing consumers, avoiding
  consumer delivery blocking when relatively long running operations (e.g. bulk flushing
  of transient messages to disk) happen.

  GitHub issues: rabbitmq-server#1388, rabbitmq-server#1407

• Queue master strategies now take additional queue HA arguments into account.

  GitHub issue: rabbitmq-server#1371

• Logging to standard output using RABBITMQ_LOGS=- wasn't possible on Windows.

  GitHub issue:

• Queue master locator name now can be specified as Erlang strings.

  GitHub issue: rabbitmq-server#1411

• Direct Erlang client connections could fail with obscure messages when
  target node was still booting.

  GitHub issue: rabbitmq-server#1356

Enhancements

• supervisor2 now can be used in environments that perform hot code upgrades.

  GitHub issue: rabbitmq-common#230

• systemd service file now white lists exit code 69.

  GitHub issue: rabbitmq-server-release#51

• Example systemd service file now includes service restart settings.

  GitHub issue: rabbitmq-server#1359

• Plugin activation avoids logs things that can be confusing.

  GitHub issue: rabbitmq-server#1364

Management Plugin

Enhancements

• Minor efficiency improvements around stats collection.

  GitHub issues: rabbitmq-common#235

• jQuery upgraded to 1.10.

  GitHub issue: rabbitmq-management#494

• UI improvements.

• Queue details page no longer truncates node name.

  GitHub issue: rabbitmq-management#473

• Policy name in queue and exchange info is now a link.

  GitHub issue: rabbitmq-management#493

• DELETE /api/connections/{name} is now more defensive.

  GitHub issue: rabbitmq-management#497

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

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-3.6.13.tar.gz.

RabbitMQ 3.7.0-rc.1

Release Highlights

These are release notes for RabbitMQ 3.7.0 RC1, a candidate of a feature release.

This release introduces new features, changes to RabbitMQ distribution (e.g. what plugins ship
with it), and bug fixes. It also includes all the changes from the 3.6.x release series unless stated otherwise.

Documentation for this preview is available at next.rabbitmq.com.

Breaking Changes

• Minimum required Erlang/OTP version is now 19.2. Recent Erlang versions can be obtained from Erlang Solutions, RabbitMQ zero dependency Erlang RPM, as well as main and backports repositories of recent Ubuntu and Debian releases.

  GitHub issues: rabbitmq-server#1305, rabbitmq-server#1307.

• .NET client is now .NET Core-compatible.
  Starting with 3.7.0, .NET client releases are decoupled from RabbitMQ server releases and exclusively distributed via the RabbitMQ.Client NuGet package.

• Starting with 3.7.0, Java client releases are decoupled from RabbitMQ server releases and exclusively distributed via Maven: RabbitMQ Milestones Maven repository, RabbitMQ Maven repository, as well as Maven Central.

• Users tagged with administrator now implicitly have access to most operations in all vhosts,
  including those they don't have explicit permissions for.

  GitHub issue: rabbitmq-management#461

• Plugins now must depend on the rabbit application in order to be recognised as such by rabbitmq-plugins list.
  Plugins that do not have the dependency will still function, can be enabled or disabled but won't appear
  in rabbitmq-plugins list output.

• rabbitmq_management_visualiser plugin no longer ships with RabbitMQ and is considered to be deprecated.

Erlang/OTP 20 Support

Erlang/OTP 20 has breaking changes that affected RabbitMQ.

3.7.0 supports OTP 20, including upgrades of existing installations to OTP 20.
This required changes to the core and multiple plugins that ship with RabbitMQ.

GitHub issues: rabbitmq-server#1243, rabbitmq-server#1250, rabbitmq-server#1268,
rabbitmq-server#1272, rabbitmq-federation#58, rabbitmq-management-agent#47,
rabbitmq-management#415, rabbitmq-stomp#115

Core Server

Enhancements

• New configuration file format

  RabbitMQ now supports a new configuration file format.
  The format is based on sysctl
  and is similar to .ini files. Erlang term configuration files are still supported, it is also
  possible to combine the two formats (use both rabbitmq.conf and advanced.config).

  Most documentation examples were updated to use both new and classic config formats. See the docs
  at next.rabbitmq.com, in particular the configuration guide,
  for more information.

  GitHub issues: rabbitmq-server#550,
  rabbitmq-server#1103,
  rabbitmq-auth-backend-ldap#59

• Pluggable cluster peer discovery

  Automatic clustering for blank (without an existing database) nodes now can discover
  peers using pluggable backends. This is a set of features adopted from the rabbitmq-autocluster plugin by Gavin Roy.
  Two implementations are available out of the box: one uses a config file- and another DNS A records.
  Several more are available via plugins:

  • AWS
  • Consul
  • etcd
  • Kubernetes

  GitHub issues: rabbitmq-server#486, rabbitmq-server#988, rabbitmq-server#1143
  rabbitmq-server#1202, rabbitmq-server#1171, rabbitmq-server#1257, rabbitmq-server#1247

• Nodes in a cluster now can be restared in arbitrary order. They will attempt to contact
  one of the previously seen peers periodically (10 times with 30 second intervals by default).

  GitHub issue: rabbitmq-server#1022,
  rabbitmq-server#487

• CLI tools were significatnly redesigned,
  now can be extended from plugins and support command
    aliases (à la Git). There's also a new tool, rabbitmq-diagnostics, and several new commands available.

  GitHub issues: rabbitmq-server#577, rabbitmq-cli#38, rabbitmq-server#1085,
  rabbitmq-cli#10, rabbitmq-cli#178, rabbitmq-cli#180.

• Every virtual host now has separate message stores.
  This improves resiliency and reduces contention in multitenant environments,
  plus makes development of tools that perform backups and recovery of resting data easier
  in the future.

  During the upgrade nodes will migrate data to this new layout. This can take some time.
  To reduce the amount of time, drain as many queues as possible before upgrading, e.g.
  by stopping publishers without stopping consumers for a period of time.

  GitHub issues: rabbitmq-server#567, rabbitmq-server#1146, rabbitmq-server#1280,
  rabbitmq-management#446, rabbitmq-server#1303, rabbitmq-management#460, rabbitmq-server#1321

• New LevelDB-based message store index plugin.

  GitHub issue: rabbitmq-server#838

• Support config file path values with and without file extensions

  RabbitMQ no longer requires RABBITMQ_CONFIG_FILE values to not have a .config or .conf suffix. It will try appending both suffixes as needed when searching for suitable config file(s) to load.

  Github Issue: rabbitmq-server#691

• Operators now can configure how many concurrent connections are allowed in a vhost.

  GitHub issue: rabbitmq-server#500

• Operators now can configure how many queues can exist in a vhost.

  GitHub issue: rabbitmq-server#501

• Operator policies: their definitions are merged with the standard (user) policies and allow operators put global
  limits in place, e.g. max queue length or message TTL.

  GitHub issue: rabbitmq-server#930

• Plugin version constraints

  RabbitMQ now has a mechanism for plugin authors to indicate what versions a plugin is compatible with.
  Incompatible plugins are logged and ignored.

  Github issues: rabbitmq-server#591, [rabbitmq-server#735](https://github.com/rabbitmq/rabbitmq-server/issues...

RabbitMQ 3.7.0 Milestone 20

Release Highlights

This is the release notes for RabbitMQ 3.7.0 Milestone 20. This is a preview of
a feature release that's expected to ship in 2017.

Breaking Changes

• Minimum required Erlang/OTP version is now 19.2. Recent Erlang versions can be obtained from Erlang Solutions, RabbitMQ zero dependency Erlang RPM, as well as main and backports repositories of recent Ubuntu and Debian releases.

  GitHub issues: rabbitmq-server#1305, rabbitmq-server#1307.

• .NET client is now .NET Core-compatible.
  Starting with 3.7.0, .NET client releases are decoupled from RabbitMQ server releases and exclusively distributed via the RabbitMQ.Client NuGet package.

• Starting with 3.7.0, Java client releases are decoupled from RabbitMQ server releases and exclusively distributed via Maven: RabbitMQ Milestones Maven repository, RabbitMQ Maven repository, as well as Maven Central.

• Users tagged with administrator now implicitly have access to most operations in all vhosts,
  including those they don't have explicit permissions for.

  GitHub issue: rabbitmq-management#461

• Plugins now must depend on the rabbit application in order to be recognised as such by rabbitmq-plugins list.
  Plugins that do not have the dependency will still function, can be enabled or disabled but won't appear
  in rabbitmq-plugins list output.

• rabbitmq_management_visualiser plugin no longer ships with RabbitMQ and is considered to be deprecated.

Erlang/OTP 20 Support

Erlang/OTP 20 has breaking changes that affected RabbitMQ.

3.7.0 supports OTP 20, including upgrades of existing installations to OTP 20.
This required changes to the core and multiple plugins that ship with RabbitMQ.

GitHub issues: rabbitmq-server#1243, rabbitmq-server#1250, rabbitmq-server#1268,
rabbitmq-server#1272, rabbitmq-federation#58, rabbitmq-management-agent#47,
rabbitmq-management#415, rabbitmq-stomp#115

Core Server

Enhancements

• New configuration file format

  RabbitMQ now supports a new configuration file format.
  The format is based on sysctl
  and is similar to .ini files. Erlang term configuration files are still supported, it is also
  possible to combine the two formats (use both rabbitmq.conf and advanced.config).

  Most documentation examples were updated to use both new and classic config formats. See the docs
  at next.rabbitmq.com, in particular the configuration guide,
  for more information.

  GitHub issues: rabbitmq-server#550,
  rabbitmq-server#1103,
  rabbitmq-auth-backend-ldap#59

• Pluggable cluster peer discovery

  Automatic clustering for blank (without an existing database) nodes now can discover
  peers using pluggable backends. This is a set of features adopted from the rabbitmq-autocluster plugin by Gavin Roy.
  Two implementations are available out of the box: one uses a config file- and another DNS A records.
  Several more are available via plugins:

  • AWS
  • Consul
  • etcd
  • Kubernetes

  GitHub issues: rabbitmq-server#486, rabbitmq-server#988, rabbitmq-server#1143
  rabbitmq-server#1202, rabbitmq-server#1171, rabbitmq-server#1257, rabbitmq-server#1247

• Nodes in a cluster now can be restared in arbitrary order. They will attempt to contact
  one of the previously seen peers periodically (10 times with 30 second intervals by default).

  GitHub issue: rabbitmq-server#1022,
  rabbitmq-server#487

• CLI tools were significatnly redesigned,
  now can be extended from plugins and support command
    aliases (à la Git). There's also a new tool, rabbitmq-diagnostics, and several new commands available.

  GitHub issues: rabbitmq-server#577, rabbitmq-cli#38, rabbitmq-server#1085,
  rabbitmq-cli#10, rabbitmq-cli#178, rabbitmq-cli#180.

• Every virtual host now has separate message stores.
  This improves resiliency and reduces contention in multitenant environments,
  plus makes development of tools that perform backups and recovery of resting data easier
  in the future.

  During the upgrade nodes will migrate data to this new layout. This can take some time.
  To reduce the amount of time, drain as many queues as possible before upgrading, e.g.
  by stopping publishers without stopping consumers for a period of time.

  GitHub issues: rabbitmq-server#567, rabbitmq-server#1146, rabbitmq-server#1280,
  rabbitmq-management#446, rabbitmq-server#1303, rabbitmq-management#460, rabbitmq-server#1321

• New LevelDB-based message store index plugin.

  GitHub issue: rabbitmq-server#838

• Support config file path values with and without file extensions

  RabbitMQ no longer requires RABBITMQ_CONFIG_FILE values to not have a .config or .conf suffix. It will try appending both suffixes as needed when searching for suitable config file(s) to load.

  Github Issue: rabbitmq-server#691

• Operators now can configure how many concurrent connections are allowed in a vhost.

  GitHub issue: rabbitmq-server#500

• Operators now can configure how many queues can exist in a vhost.

  GitHub issue: rabbitmq-server#501

• Operator policies: their definitions are merged with the standard (user) policies and allow operators put global
  limits in place, e.g. max queue length or message TTL.

  GitHub issue: rabbitmq-server#930

• Plugin version constraints

  RabbitMQ now has a mechanism for plugin authors to indicate what versions a plugin is compatible with.
  Incompatible plugins are logged and ignored.

  Github issues: rabbitmq-server#591, rabbitmq-server#735, rabbitmq-server#1090

• Lager-based logging: less not prone to overload, pluggable backends, debug log level, more flexibility in configuration.

  RabbitMQ...

RabbitMQ 3.6.12

RabbitMQ 3.6.12

RabbitMQ 3.6.12 is a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.11.
See the upgrade and compatibility sections in the 3.6.7 release notes if upgrading from an earlier release.

Core Server

Bug Fixes

• Process responsible for running the autoheal partition handling strategy
  could run into a deadlock with its peers, preventing autoheal from completing.

  GitHub issue: rabbitmq-server#1346

• Garbage collection of mirrored queue metrics on nodes that did not
  host a master or mirror for a queue affected delivery and acknowledgement rates.
  This could result in rates being 0 or negative when they should not be.

  GitHub issue: rabbitmq-server#1340

• Stats emission could prevent queue mirrors from performing garbage collection
  and consume memory even when they were empty.

  GitHub issue: rabbitmq-common#220 (continuation to rabbitmq-common#196)

• RABBITMQ_SCHEDULER_BIND_TYPE and RABBITMQ_DISTRIBUTION_BUFFER_SIZE now can be set via rabbitmq-env.conf.

  GitHub issue: rabbitmq-server#1338

Shovel Management Plugin

Bug Fixes

• Passwords in source and destination URIs are now redacted out.

  GitHub issue: rabbitmq-federation-management#15

Federation Management Plugin

Bug Fixes

• Passwords in upstream URIs are now redacted out.

  GitHub issue: rabbitmq-federation-management#15

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

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-3.6.12.tar.gz.

RabbitMQ 3.6.12 RC3

RabbitMQ 3.6.12 RC3

RabbitMQ 3.6.12 RC3 is a preview of a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.10.
See the upgrade and compatibility sections in the 3.6.7 release notes if upgrading from an earlier release.

Core Server

Bug Fixes

• Process responsible for running the autoheal partition handling strategy
  could run into a deadlock with its peers, preventing autoheal from completing.

  GitHub issue: rabbitmq-server#1346

• Garbage collection of mirrored queue metrics on nodes that did not
  host a master or mirror for a queue affected delivery and acknowledgement rates.
  This could result in rates being 0 or negative when they should not be.

  GitHub issue: rabbitmq-server#1340

• Stats emission could prevent queue mirrors from performing garbage collection
  and consume memory even when they were empty.

  GitHub issue: rabbitmq-common#220 (continuation to rabbitmq-common#196)

• RABBITMQ_SCHEDULER_BIND_TYPE and RABBITMQ_DISTRIBUTION_BUFFER_SIZE now can be set via rabbitmq-env.conf.

  GitHub issue: rabbitmq-server#1338

Shovel Management Plugin

Bug Fixes

• Passwords in source and destination URIs are now redacted out.

  GitHub issue: rabbitmq-federation-management#15

Federation Management Plugin

Bug Fixes

• Passwords in upstream URIs are now redacted out.

  GitHub issue: rabbitmq-federation-management#15

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

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-3.6.12.tar.gz.

RabbitMQ 3.6.12 RC2

RabbitMQ 3.6.12 RC2

RabbitMQ 3.6.12 RC2 is a preview of a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.11.
See 3.6.7 release notes
upgrade and compatibility sections if upgrading from an earlier release.

Core Server

Bug Fixes

• Garbage collection of mirrored queue metrics on nodes that did not
  host a master or mirror for a queue affected delivery and acknowledgement rates.
  This could result in rates being 0 or negative when they should not be.

  GitHub issue: rabbitmq-server#1340

• Stats emission could prevent queue mirrors from performing garbage collection
  and consume memory even when they were empty.

  GitHub issue: rabbitmq-common#220 (continuation to rabbitmq-common#196)

• RABBITMQ_SCHEDULER_BIND_TYPE and RABBITMQ_DISTRIBUTION_BUFFER_SIZE now can be set via rabbitmq-env.conf.

  GitHub issue: rabbitmq-server#1338

Shovel Management Plugin

Bug Fixes

• Passwords in source and destination URIs are now redacted out.

  GitHub issue: rabbitmq-federation-management#15

Federation Management Plugin

Bug Fixes

• Passwords in upstream URIs are now redacted out.

  GitHub issue: rabbitmq-federation-management#15

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

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-3.6.12.tar.gz.

RabbitMQ 3.6.12 RC1

RabbitMQ 3.6.12 RC1

RabbitMQ 3.6.12 RC1 is a preview of a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.11.
See 3.6.7 release notes
upgrade and compatibility sections if upgrading from an earlier release.

Core Server

Bug Fixes

• Garbage collection of mirrored queue metrics on nodes that did not
  host a master or mirror for a queue affected delivery and acknowledgement rates.
  This could result in rates being 0 or negative when they should not be.

  GitHub issue: rabbitmq-server#1340

• RABBITMQ_SCHEDULER_BIND_TYPE and RABBITMQ_DISTRIBUTION_BUFFER_SIZE now can be set via rabbitmq-env.conf.

  GitHub issue: rabbitmq-server#1338

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
When upgrading using definitions export/import from versions earlier than 3.6.0, see http://rabbitmq.com/passwords.html.

To upgrade a RabbitMQ cluster, follow the instructions in RabbitMQ documentation.

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-3.6.12.tar.gz.

RabbitMQ 3.6.11

RabbitMQ 3.6.11

RabbitMQ 3.6.11 is a maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

⚠️ This release changes how nodes compute the amount of RAM they use (and report). Previously the value was underreported.
We recommend monitoring — or at least manually sampling — the RSS of
the Erlang VM running RabbitMQ, comparing it to the value reported in the management UI
to compute the delta. Then adjust configured VM high memory watermark an
possibly provisioning more RAM as needed.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.10.
See the upgrade and compatibility sections in the 3.6.7 release notes if upgrading from an earlier release.

⚠️ This is the first release that supports Erlang/OTP 20.

Core Server

Bug Fixes

• Node RAM consumption calculation strategy has changed
  to a more precise one. Previously the value was underreported. It is possible to switch to the behavior in earlier versions
  if desired. This will affect monitoring charts and possibly require bumping VM memory high watermark
  or provisioning more RAM.

  GitHub issue: rabbitmq-server#1223, rabbitmq-server#1270

• Erlang/OTP 20 is now supported.

  GitHub issues: rabbitmq-server#1243, rabbitmq-server#1246, rabbitmq-federation#58, rabbitmq-management-agent#47, rabbitmq-management#415, rabbitmq-stomp#115

• supervisor2: supervisor could fail to restart failed child processes in some cases.
  This could affect multiple plugins, e.g. federation.

  Contributed by Aliaksey Artamonau (Couchbase).

  GitHub issues: rabbitmq-common#201,
  rabbitmq-server#1238

• Memory used by binary heap ("binaries") was reduced for some scenarios that involve mirrored queues.

  GitHub issue: rabbitmq-common#208

• Exclusive queues were not cleaned up when node failed or was considered unavailable by one of its
  peers.

  GitHub issue: rabbitmq-server#1323

• rabbitmq-service.bat start and rabbitmq-service.bat stop did not report access violation
  errors.

  GitHub issue: rabbitmq-server#1324

• When high VM memory watermarked is set to a value greater than 1.0,
  1.0 will be used as effective value now instead of the default (0.4).

  GitHub issue: rabbitmq-server#1285

Enhancements

• Total amount of RAM as seen by a node now can be overridden via config file.

  GitHub issue: rabbitmq-server#1224

• Default value of RABBITMQ_DISTRIBUTION_BUFFER_SIZE is now 128000. This makes inter-node communication
  throughput more stable on 1 GBbit/s (or greater) network links.

  GitHub issue: rabbitmq-server#1306

• Plugins that are already expanded (unarhived from .ez archives on node boot) won't be
  expanded again.

  Contributed by Alex Lebedeff (Mirantis).

  GitHub issue: rabbitmq-server#1226

Management plugin

Enhancements

• Listing queues, exchanges, vhosts via HTTP API is now more efficient for common cases
  (e.g. when pagination is not used or only a subset of fields is requested).

  GitHub issue: rabbitmq-management#402

• Inter-node cluster link traffic information was missing.

  GitHub issue: rabbitmq-management#434

• Exclusive queues didn't have feature markers in the UI.

  GitHub issue: rabbitmq-management#459

• Queue master locator now has a feature marker in the UI.

  GitHub issue: rabbitmq-management#468

• It is now possible to pre-configure user permission at the time of its creation.

  GitHub issue: rabbitmq-management#441

• rabbitmqadmin now supports --ssl-insecure (-k), serving the same purpose as -k in curl

  GitHub issue: rabbitmq-management#452

• rabbitmqadmin now supports setting HTTP API endpoint hostname, port, username, and password
  using a URI.

  GitHub issue: rabbitmq-management#437

• HTTP API requests now are less likely to produce log noise.

  GitHub issue: rabbitmq-web-dispatch#27

Bug Fixes

• Queue master migration no longer leaves statistics database records behind.

  GitHub issue: rabbitmq-management#427

• Consumer argument serialisation to JSON was fixed.

  GitHub issue: rabbitmq-management#424

• It is now again possible to create a user without a password (or password hash).
  Such users won't be able to sign in with internal authentication backend
  but can be used with external authentication mechanisms (x509 certificates) and backends
  (LDAP, HTTP, etc).

  GitHib issue: rabbitmq-management#383

• Pagination combined with a user-provided set of columns returned no results.

  GitHub issue: rabbitmq-management#404

• Regular expressions used for filtering were not correctly escaped.

  GitHub issue: rabbitmq-management#419

• rabbitmqadmin now handles float rates.

  GitHub issue: rabbitmq-management#457

• rabbitmqadmin now ignores SIGPIPE signals and much less likely to terminate when its output is piped to
  another process.

  GitHub issue: rabbitmq-management#438

• HTTP requests with unintialised fields are less likely to crash log event handler.

  GitHub issue: rabbitmq-web-dispatch#27

Federation Plugin

Bug Fixes

• Federation links now recover better in certain scenarios, e.g. when one side of a link could be reset.

  GitHub issue: rabbitmq-federation#59

STOMP Plugin

Bug Fixes

• Erlang/OTP 20 is now supported.

  GitHub issue: rabbitmq-stomp#115

MQTT Plugin

Enhancements

• No-op MQTT message retainer.

  GitHub issue: rabbitmq-mqtt#136

Bug Fixes

• MQTT connection processes now use connection log level.

  GitHub issue: rabbitmq-mqtt#142

Consistent Hashing Exchange

Bug Fixes

• Bucket distribution is now consistent (doesn't change) between plugin and node restarts
  (assuming bindings haven't changed).

  GitHub issue: rabbitmq-consistent-hash-exchange#32

Top Plugin

Bug Fixes

• rabbitmq-top now gracefully covers scenarios when it is enabled only on a subset of cluster nodes.

  GitHub issue: rabbitmq-top#23

• Node drop down on ETS table tab redirected to the processes tab.

  GitHub issue: rabbitmq-top#24

Message Timestamp Plugin

Enhancements

• Timestamp in milliseconds is also injected as a header (unless the header is present).

  GitHub issue: rabbitmq-message-timestamp#16

Upgrading

To upgrade a non-clustered RabbitMQ simply instal...

RabbitMQ 3.6.11 RC3

RabbitMQ 3.6.11 RC3

RabbitMQ 3.6.11 RC3 is a preview of maintenance release.

Upgrades and Compatibility

See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.

⚠️ This release changes how nodes compute the amount of RAM they use (and report). Previously the value was underreported.
We recommend monitoring — or at least manually sampling — the RSS of
the Erlang VM running RabbitMQ, comparing it to the value reported in the management UI
to compute the delta. Then adjust configured VM high memory watermark an
possibly provisioning more RAM as needed.

This release has no other known incompatibilities with versions 3.6.7 through 3.6.10.
See 3.6.7 release notes
upgrade and compatibility sections if upgrading from an earlier release.

⚠️ This is the first release that supports Erlang/OTP 20.

Core Server

Bug Fixes

• Node RAM consumption calculation strategy has changed
  to a more precise one. Previously the value was underreported. It is possible to switch to the behavior in earlier versions
  if desired. This will affect monitoring charts and possibly require bumping VM memory high watermark
  or provisioning more RAM.

  GitHub issue: rabbitmq-server#1243, rabbitmq-server#1246, rabbitmq-server#1270

• Erlang/OTP 20 is now supported.

  GitHub issues: rabbitmq-server#1243, rabbitmq-server#1246, rabbitmq-federation#58, rabbitmq-management-agent#47, rabbitmq-management#415, rabbitmq-stomp#115

• supervisor2: supervisor could fail to restart failed child processes in some cases.
  This could affect multiple plugins, e.g. federation.

  Contributed by Aliaksey Artamonau (Couchbase).

  GitHub issues: rabbitmq-common#201,
  rabbitmq-server#1238

• Memory used by binary heap ("binaries") was reduced for some scenarios that involve mirrored queues.

  GitHub issue: rabbitmq-common#208

• Exclusive queues were not cleaned up when node failed or was considered unavailable by one of its
  peers.

  GitHub issue: rabbitmq-server#1323

• rabbitmq-service.bat start and rabbitmq-service.bat stop did not report access violation
  errors.

  GitHub issue: rabbitmq-server#1324

• When high VM memory watermarked is set to a value greater than 1.0,
  1.0 will be used as effective value now instead of the default (0.4).

  GitHub issue: rabbitmq-server#1285

Enhancements

• Total amount of RAM as seen by a node now can be overridden via config file.

  GitHub issue: rabbitmq-server#1224

• Default value of RABBITMQ_DISTRIBUTION_BUFFER_SIZE is now 128000. This makes inter-node communication
  throughput more stable on 1 GBbit/s (or greater) network links.

  GitHub issue: rabbitmq-server#1306

• Plugins that are already expanded (unarhived from .ez archives on node boot) won't be
  expanded again.

  Contributed by Alex Lebedeff (Mirantis).

  GitHub issue: rabbitmq-server#1226

Management plugin

Enhancements

• Listing queues, exchanges, vhosts via HTTP API is now more efficient for common cases
  (e.g. when pagination is not used or only a subset of fields is requested).

  GitHub issue: rabbitmq-management#402

• Inter-node cluster link traffic information was missing.

  GitHub issue: rabbitmq-management#434

• Exclusive queues didn't have feature markers in the UI.

  GitHub issue: rabbitmq-management#459

• It is now possible to pre-configure user permission at the time of its creation.

  GitHub issue: rabbitmq-management#441

• rabbitmqadmin now supports --ssl-insecure (-k), serving the same purpose as -k in curl

  GitHub issue: rabbitmq-management#452

• rabbitmqadmin now supports setting HTTP API endpoint hostname, port, username, and password
  using a URI.

  GitHub issue: rabbitmq-management#437

• HTTP API requests now are less likely to produce log noise.

  GitHub issue: rabbitmq-web-dispatch#27

Bug Fixes

• Queue master migration no longer leaves statistics database records behind.

  GitHub issue: rabbitmq-management#427

• Consumer argument serialisation to JSON was fixed.

  GitHub issue: rabbitmq-management#424

• It is now again possible to create a user without a password (or password hash).
  Such users won't be able to sign in with internal authentication backend
  but can be used with external authentication mechanisms (x509 certificates) and backends
  (LDAP, HTTP, etc).

  GitHib issue: rabbitmq-management#383

• Pagination combined with a user-provided set of columns returned no results.

  GitHub issue: rabbitmq-management#404

• Regular expressions used for filtering were not correctly escaped.

  GitHub issue: rabbitmq-management#419

• rabbitmqadmin now handles float rates.

  GitHub issue: rabbitmq-management#457

• rabbitmqadmin now ignores SIGPIPE signals and much less likely to terminate when its output is piped to
  another process.

  GitHub issue: rabbitmq-management#438

• HTTP requests with unintialised fields are less likely to crash log event handler.

  GitHub issue: rabbitmq-web-dispatch#27

Federation Plugin

Bug Fixes

• Federation links now recover better in certain scenarios, e.g. when one side of a link could be reset.

  GitHub issue: rabbitmq-federation#59

STOMP Plugin

Bug Fixes

• Erlang/OTP 20 is now supported.

  GitHub issue: rabbitmq-stomp#115

MQTT Plugin

Enhancements

• No-op MQTT message retainer.

  GitHub issue: rabbitmq-mqtt#136

Bug Fixes

• MQTT connection processes now use connection log level.

  GitHub issue: rabbitmq-mqtt#142

Consistent Hashing Exchange

Bug Fixes

• Bucket distribution is now consistent (doesn't change) between plugin and node restarts
  (assuming bindings haven't changed).

  GitHub issue: rabbitmq-consistent-hash-exchange#32

Top Plugin

Bug Fixes

• rabbitmq-top now gracefully covers scenarios when it is enabled only on a subset of cluster nodes.

  GitHub issue: rabbitmq-top#23

• Node drop down on ETS table tab redirected to the processes tab.

  GitHub issue: rabbitmq-top#24

Message Timestamp Plugin

Enhancements

• Timestamp in milliseconds is also injected as a header (unless the header is present).

  GitHub issue: rabbitmq-message-timestamp#16

Upgrading

To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
Wh...