3.6.11 is a maintenance release.
Upgrades and Compatibility
See the "Upgrading clusters" section of the documentation
for general documentation on upgrades.
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.
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.
Erlang/OTP 20 is now supported.
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).
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
GitHub issue: rabbitmq-server#1323
rabbitmq-service.bat stopdid not report access violation
GitHub issue: rabbitmq-server#1324
When high VM memory watermarked is set to a value greater than 1.0,
1.0will be used as effective value now instead of the default (
GitHub issue: rabbitmq-server#1285
Total amount of RAM as seen by a node now can be overridden via config file.
GitHub issue: rabbitmq-server#1224
Default value of
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
.ezarchives on node boot) won't be
Contributed by Alex Lebedeff (Mirantis).
GitHub issue: rabbitmq-server#1226
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
-k), serving the same purpose as
GitHub issue: rabbitmq-management#452
rabbitmqadminnow 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
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
rabbitmqadminnow handles float rates.
GitHub issue: rabbitmq-management#457
SIGPIPEsignals and much less likely to terminate when its output is piped to
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 links now recover better in certain scenarios, e.g. when one side of a link could be reset.
GitHub issue: rabbitmq-federation#59
No-op MQTT message retainer.
GitHub issue: rabbitmq-mqtt#136
MQTT connection processes now use connection log level.
GitHub issue: rabbitmq-mqtt#142
Consistent Hashing Exchange
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
rabbitmq-topnow 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
Timestamp in milliseconds is also injected as a header (unless the header is present).
GitHub issue: rabbitmq-message-timestamp#16
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