|
| 1 | +## RabbitMQ 4.3.0 |
| 2 | + |
| 3 | +RabbitMQ `4.3.0` is a new feature release. |
| 4 | + |
| 5 | + |
| 6 | +## Breaking Changes and Compatibility Notes |
| 7 | + |
| 8 | +### Classic Queues v1 Storage (CQv1) is Removed |
| 9 | + |
| 10 | +This release removes the original classic queue storage implementation these days |
| 11 | +known as CQv1. A 2nd generation implementation called CQv2 has been adopted |
| 12 | +as the default starting with `4.2.0`. |
| 13 | + |
| 14 | +This means that attemptes to declare a queue using the following [optional queue arguments](https://www.rabbitmq.com/docs/queues#optional-arguments) will fail: |
| 15 | + |
| 16 | + * `x-queue-mode` set to any value |
| 17 | + * `x-queue-version` set to `1` |
| 18 | + |
| 19 | +Existing classic queues upgraded to CQv2 during an earlier upgrade to `4.2.x` will continue |
| 20 | +operating as usual. |
| 21 | + |
| 22 | + |
| 23 | +## Release Highlights |
| 24 | + |
| 25 | +TBD |
| 26 | + |
| 27 | + |
| 28 | +## Upgrading to 4.3.0 |
| 29 | + |
| 30 | +### Documentation guides on upgrades |
| 31 | + |
| 32 | +See the [Upgrading guide](https://www.rabbitmq.com/docs/upgrade) for documentation on upgrades and [GitHub releases](https://github.com/rabbitmq/rabbitmq-server/releases) |
| 33 | +for release notes of individual releases. |
| 34 | + |
| 35 | +This release series supports upgrades from `4.2.x`. Upgrades from earlier series are **not** supported: |
| 36 | +users must upgrade to the latest available `4.2.x` patch release before upgrading to `4.3.0`. |
| 37 | + |
| 38 | + |
| 39 | +### New Required Feature Flags |
| 40 | + |
| 41 | +All feature flags introduced in `4.2.0` and earlier are required, including the following: |
| 42 | +* `rabbitmq_4.2.0` |
| 43 | +* `rabbitmq_4.1.0` |
| 44 | +* `rabbitmq_4.0.0` |
| 45 | +* `khepri_db` |
| 46 | +* `quorum_queue_non_voters` |
| 47 | +* `message_containers_deaths_v2` |
| 48 | + |
| 49 | +Enable all required feature flags before upgrading to `4.3.0`. |
| 50 | + |
| 51 | +If your RabbitMQ cluster had plugin `rabbitmq_amqp1_0` enabled in RabbitMQ `3.13.x` (and your cluster still serves AMQP 1.0 client connections in `4.x`), your cluster should do at least one rolling update **after** enabling feature flag `rabbitmq_4.0.0` but **before** upgrading to `4.3.0`. |
| 52 | + |
| 53 | +### Deprecated Features |
| 54 | + |
| 55 | +In `4.3.0` the deprecation phase of the following features advanced from `permitted_by_default` to `denied_by_default`: |
| 56 | +* `amqp_filter_set_bug` |
| 57 | + |
| 58 | +### Mixed version cluster compatibility |
| 59 | + |
| 60 | +RabbitMQ 4.3.0 nodes can run alongside `4.2.x`. |
| 61 | + |
| 62 | +Mixed version clusters are a mechanism that allows rolling upgrade and are not meant to be run for extended |
| 63 | +periods of time (no more than a few hours). |
| 64 | + |
| 65 | +### Recommended Post-upgrade Procedures |
| 66 | + |
| 67 | +This version does not require any additional post-upgrade procedures |
| 68 | +compared to other versions. |
| 69 | + |
| 70 | + |
| 71 | +## Changes Worth Mentioning |
| 72 | + |
| 73 | +### Core Server |
| 74 | + |
| 75 | +#### Bug Fixes |
| 76 | + |
| 77 | + * Quorum queue at-most-once dead lettering for the overflow behaviour `drop-head` now happens in the correct order. |
| 78 | + |
| 79 | + GitHub issue: [#14926](https://github.com/rabbitmq/rabbitmq-server/pull/14926) |
| 80 | + |
| 81 | + * Feature flag state in the registry and on disk were not consistent for a period of time during node boot. |
| 82 | + |
| 83 | + GitHub issue: [#14943](https://github.com/rabbitmq/rabbitmq-server/pull/14943) |
| 84 | + |
| 85 | + |
| 86 | +### Stream Plugin |
| 87 | + |
| 88 | +#### Bug Fixes |
| 89 | + |
| 90 | + * `stream.read_ahead` is a new setting that controls how much data is prefetched from disk |
| 91 | + for stream reads (consumption). |
| 92 | + |
| 93 | + GitHub issue: [#14948/](https://github.com/rabbitmq/rabbitmq-server/pull/14948) |
| 94 | + |
| 95 | + * Stream deletion is now more resilient and can handle certain mid-deletion failure scenarios. |
| 96 | + |
| 97 | + GitHub issue: [#14852](https://github.com/rabbitmq/rabbitmq-server/issues/14852) |
| 98 | + |
| 99 | + |
| 100 | +### Grafana Dashboards |
| 101 | + |
| 102 | +#### Enhancements |
| 103 | + |
| 104 | + * The [dashboards](https://grafana.com/orgs/rabbitmq) were updated for the most recent RabbitMQ release series. |
| 105 | + |
| 106 | + |
| 107 | +### Management Plugin |
| 108 | + |
| 109 | +#### Enhancements |
| 110 | + |
| 111 | + * `GET /api/queues/{vhost}` requests no longer perform unnecessary virtual host permission checks |
| 112 | + and log less (at `debug` level) as a result. |
| 113 | + |
| 114 | + GitHub issue: [#14923](https://github.com/rabbitmq/rabbitmq-server/discussions/14923) |
| 115 | + |
| 116 | + |
| 117 | +### Tracing Plugin |
| 118 | + |
| 119 | +#### Bug Fixes |
| 120 | + |
| 121 | + * Trace file downloads now correctly display Cyrillic and other Unicode characters in browsers |
| 122 | + by setting `charset=utf-8` in the `Content-Type` header. |
| 123 | + |
| 124 | + GitHub issue: [#13952](https://github.com/rabbitmq/rabbitmq-server/issues/13952) |
| 125 | + |
| 126 | + |
| 127 | +### Shovel Plugin |
| 128 | + |
| 129 | +#### Bug Fixes |
| 130 | + |
| 131 | + * Improved target node resource alarm handling for AMQP 1.0 and local shovels. |
| 132 | + |
| 133 | + GitHub issue: [#14886](https://github.com/rabbitmq/rabbitmq-server/pull/14886) |
| 134 | + |
| 135 | + * Local shovels could run into an exception that would cause a shovel restart. |
| 136 | + |
| 137 | + GitHub issue: [#14872](https://github.com/rabbitmq/rabbitmq-server/pull/14872) |
| 138 | + |
| 139 | + * AMQP 1.0 shovels ignored the `sasl` URI parameter. |
| 140 | + |
| 141 | + GitHub issue: [#14867](https://github.com/rabbitmq/rabbitmq-server/pull/14867) |
| 142 | + |
| 143 | + |
| 144 | +### OAuth 2 Plugin |
| 145 | + |
| 146 | +#### Bug Fixes |
| 147 | + |
| 148 | + * A usability improvement allows the plugin to automatically load the trusted system x.509 (TLS) certificates. |
| 149 | + |
| 150 | + GitHub issue: [#14927](https://github.com/rabbitmq/rabbitmq-server/pull/14927) |
| 151 | + |
| 152 | + |
| 153 | +### LDAP Plugin |
| 154 | + |
| 155 | +#### Enhancements |
| 156 | + |
| 157 | + * LDAP queries, including multi-line ones, now can be specified in `rabbitmq.conf`. |
| 158 | + |
| 159 | + GitHub issue: [#14868](https://github.com/rabbitmq/rabbitmq-server/pull/14868) |
| 160 | + |
| 161 | +#### Bug Fixes |
| 162 | + |
| 163 | + * A usability improvement allows the plugin to automatically load the trusted system certificates |
| 164 | + when the user only enables TLS for the LDAP client but does not configure any other settings. |
| 165 | + |
| 166 | + GitHub issue: [#14937](https://github.com/rabbitmq/rabbitmq-server/pull/14937) |
| 167 | + |
| 168 | + |
| 169 | +### HTTP Auth Backend Plugin |
| 170 | + |
| 171 | +#### Enhancements |
| 172 | + |
| 173 | + * The HTTP Auth Backend can now optionally provide a custom authorization denial reason to AMQP clients. |
| 174 | + |
| 175 | + To opt in, return `deny <Reason>` (instead of only `deny`) in the HTTP response body of your HTTP auth backend and set the following in your `rabbitmq.conf` file: |
| 176 | + |
| 177 | +```ini |
| 178 | +auth_http.authorization_failure_disclosure = true |
| 179 | +``` |
| 180 | + |
| 181 | + See the [README](https://github.com/rabbitmq/rabbitmq-server/blob/main/deps/rabbitmq_auth_backend_http/README.md) for more information. |
| 182 | + |
| 183 | + GitHub issue: [#14641](https://github.com/rabbitmq/rabbitmq-server/pull/14641) |
| 184 | + |
| 185 | + |
| 186 | +### Dependency Changes |
| 187 | + |
| 188 | + * `cuttlefish` was upgraded to [`3.6.0`](https://github.com/kyorai/cuttlefish/releases) |
| 189 | + |
| 190 | +## Source Code Archives |
| 191 | + |
| 192 | +To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-4.3.0.tar.xz` |
| 193 | +instead of the source tarball produced by GitHub. |
0 commit comments