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

RabbitMQ `3.6.11` is a maintenance release. See the for general documentation on upgrades. This release (and report). Previously the value was underreported. We recommend monitoring or at least manually sampling the [RSS of the Erlang VM](http://www.linfo.org/ps.html) running RabbitMQ, comparing it to the value reported in the management UI to compute the delta. Then adjust configured 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 if upgrading from an earlier release. This is the first release that . Node RAM consumption calculation strategy 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: , Erlang/OTP 20 is . GitHub issues: , , , , , `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: , Memory used by binary heap ("binaries") was reduced for some scenarios that involve mirrored queues. GitHub issue: Exclusive queues were not cleaned up when node failed or was considered unavailable by one of its peers. GitHub issue: `rabbitmq-service.bat start` and `rabbitmq-service.bat stop` did not report access violation errors. GitHub issue: 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: Total amount of RAM as seen by a node now can be overridden via config file. GitHub issue: Default value of `RABBITMQDISTRIBUTIONBUFFER_SIZE` is now `128000`. This makes inter-node communication throughput more stable on 1 GBbit/s (or greater) network links. GitHub issue: Plugins that are already expanded (unarhived from `.ez` archives on node boot) won't be expanded again. Contributed by Alex Lebedeff (Mirantis). GitHub issue: 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: Inter-node cluster link traffic information was missing. GitHub issue: Exclusive queues didn't have feature markers in the

GitHub issue: queue leader locator now has a feature marker in the UI. GitHub issue: It is now possible to pre-configure user permission at the time of its creation. GitHub issue: `rabbitmqadmin` now supports `--ssl-insecure` (`-k`), serving the same purpose as `-k` in curl GitHub issue: `rabbitmqadmin` now supports setting HTTP API endpoint hostname, port, username, and password using a URI. GitHub issue: HTTP API requests now are less likely to produce log noise. GitHub issue: queue leader migration no longer leaves statistics database records behind. GitHub issue: Consumer argument serialisation to JSON was fixed. GitHub issue: 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 but can be used with external authentication mechanisms (x509 certificates) and backends (LDAP, HTTP, etc). GitHib issue: Pagination combined with a user-provided set of columns returned no results. GitHub issue: Regular expressions used for filtering were not correctly escaped. GitHub issue: `rabbitmqadmin` now handles float rates. GitHub issue: `rabbitmqadmin` now ignores `SIGPIPE` signals and much less likely to terminate when its output is piped to another process. GitHub issue: HTTP requests with unintialised fields are less likely to crash log event handler. GitHub issue: Federation links now recover better in certain scenarios, e.g. when one side of a link could be reset. GitHub issue: Erlang/OTP 20 is . GitHub issue: No-op MQTT message retainer. GitHub issue: MQTT connection processes now use connection log level. GitHub issue: Bucket distribution is now consistent (doesn't change) between plugin and node restarts (assuming bindings haven't changed). GitHub issue: `rabbitmq-top` now gracefully covers scenarios when it is enabled only on a subset of cluster nodes. GitHub issue: Node drop down on ETS table tab redirected to the processes tab. GitHub issue: Timestamp in milliseconds is also injected as a header (unless the header is present). GitHub issue: 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 . 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.11.tar.gz`.