|
| 1 | +RabbitMQ `3.11.11` is a maintenance release in the `3.11.x` [release series](https://www.rabbitmq.com/versions.html). |
| 2 | + |
| 3 | +Please refer to the upgrade section from [v3.11.0 release notes](https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.11.0) |
| 4 | +if upgrading from a version prior to 3.11.0. |
| 5 | + |
| 6 | +This release requires Erlang 25. |
| 7 | +[RabbitMQ and Erlang/OTP Compatibility Matrix](https://www.rabbitmq.com/which-erlang.html) has more details on |
| 8 | +Erlang version requirements for RabbitMQ. |
| 9 | + |
| 10 | + |
| 11 | +### Minimum Supported Erlang Version |
| 12 | + |
| 13 | +As of 3.11.0, RabbitMQ requires Erlang 25. Nodes **will fail to start** on older Erlang releases. |
| 14 | + |
| 15 | +Erlang 25 as our new baseline means much improved performance on ARM64 architectures, [profiling with flame graphs](https://blog.rabbitmq.com/posts/2022/05/flame-graphs/) |
| 16 | +across all architectures, and the most recent TLS 1.3 implementation available to all RabbitMQ 3.11 users. |
| 17 | + |
| 18 | + |
| 19 | +## Changes Worth Mentioning |
| 20 | + |
| 21 | +Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://github.com/rabbitmq/rabbitmq-server/tree/v3.11.x/release-notes). |
| 22 | + |
| 23 | +### Core Server |
| 24 | + |
| 25 | +#### Bug Fixes |
| 26 | + |
| 27 | + * Streams consumers that oscillate between being active and inactive, or just happen to be |
| 28 | + temporarily become really slow, could become completely starved of deliveries. That is, |
| 29 | + their message delivery rate could drop to 0 while other consumers did not have this problem. |
| 30 | + |
| 31 | + GitHub issue: [#7638](https://github.com/rabbitmq/rabbitmq-server/pull/7638) |
| 32 | + |
| 33 | + * Stream coordinator process memory footprint is now reported correctly (and classified differently). |
| 34 | + |
| 35 | + Contributed by @gomoripeti (CloudAMQP). |
| 36 | + |
| 37 | + GitHub issue: [#7548](https://github.com/rabbitmq/rabbitmq-server/pull/7548) |
| 38 | + |
| 39 | +#### Enhancements |
| 40 | + |
| 41 | + * There is now a way to pre-configure users and their permissions for newly created virtual hosts: |
| 42 | + |
| 43 | + ``` ini |
| 44 | + default_users.qa_user.vhost_pattern = qa.* |
| 45 | + default_users.qa_user.tags = policymaker,monitoring |
| 46 | + default_users.qa_user.password = fd237824441a78cd922410af4b83f0888186a8d7 |
| 47 | + default_users.qa_user.read = .* |
| 48 | + default_users.qa_user.write = .* |
| 49 | + default_users.qa_user.configure = .* |
| 50 | + ``` |
| 51 | + This is primarily useful in environments where RabbitMQ is provided as a service but |
| 52 | + customers (clients) have control over virtual hosts. |
| 53 | + |
| 54 | + Contributed by @illotum (AWS). |
| 55 | + |
| 56 | + GitHub issue: [#7208](https://github.com/rabbitmq/rabbitmq-server/issues/7208). |
| 57 | + |
| 58 | + |
| 59 | +### STOMP Plugin |
| 60 | + |
| 61 | +#### Enhancements |
| 62 | + |
| 63 | + * Consumers on `/queue/` destinations that consume from [streams](https://rabbitmq.com/streams.html) now can specify the |
| 64 | + `x-stream-max-segment-size-bytes` setting via `SUBSCRIBE` frame headers. |
| 65 | + |
| 66 | + GitHub issues: [#7605](https://github.com/rabbitmq/rabbitmq-server/pull/7605) |
| 67 | + |
| 68 | + |
| 69 | +### etcd Peer Discovery Plugin |
| 70 | + |
| 71 | +#### Bug Fixes |
| 72 | + |
| 73 | + * Node key TTL setting was unintentionally ignored. |
| 74 | + |
| 75 | + GitHub issues: [#7554](https://github.com/rabbitmq/rabbitmq-server/issues/7554) |
| 76 | + |
| 77 | + |
| 78 | +## Dependency Upgrades |
| 79 | + |
| 80 | +None in this release. |
| 81 | + |
| 82 | + |
| 83 | +## Source Code Archives |
| 84 | + |
| 85 | +To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-3.11.11.tar.xz` |
| 86 | +instead of the source tarball produced by GitHub. |
0 commit comments