|
1 | | -# Incompatible Changes between EMQX 5.x and EMQX 6.0 |
| 1 | +# Incompatible Changes in EMQX 6.0 |
2 | 2 |
|
3 | | -## Deprecated Packages |
| 3 | +## 6.0.1 |
4 | 4 |
|
5 | | -- [#15939](https://github.com/emqx/emqx/pull/15939) Stopped releasing packages for systems that have already reached end-of-life: |
6 | | - - Debian 10 (Buster) |
7 | | - - Enterprise Linux (CentOS) 7 |
8 | | - - Ubuntu 18.04 |
9 | | - - Ubuntu 20.04 |
10 | | - - macOS 13 (Ventura) |
| 5 | +- [#16062](https://github.com/emqx/emqx/pull/16062) Fixed an issue where RocketMQ actions ignored the configured payload template and sent the entire rule output instead. |
11 | 6 |
|
12 | | -- [#16050](https://github.com/emqx/emqx/pull/16050) Stopped releasing packages for Amazon Linux 2. It will reach end-of-life on June 30, 2026. |
13 | | - |
14 | | -## Durable Sessions |
15 | | - |
16 | | -If the durable sessions feature was not enabled before, you can ignore this section. |
17 | | - |
18 | | -In EMQX 6.0, the internal representation of durable sessions and their messages has changed. |
19 | | -Clusters previously running on version 5.x with durable sessions enabled must be recreated from a clean state when upgrading to 6.0. |
20 | | - |
21 | | -For detailed upgrade instructions, see the [rolling upgrade documentation](../deploy/rolling-upgrades.md#emqx-enterprise-rolling-upgrade). |
22 | | - |
23 | | -- [#15496](https://github.com/emqx/emqx/pull/15496) The state of durable sessions has been migrated from Mnesia to a new database built on EMQX durable storage. |
24 | | - - As a result, all durable session states created before 6.0.0 will be lost during the migration. |
25 | | - - This change resolves potential session state corruption caused by Mnesia’s limited transaction isolation (see [#14039](https://github.com/emqx/emqx/issues/14039)). |
26 | | - - It also improves the performance and scalability of durable sessions through sharding and a more efficient data representation. |
27 | | - |
28 | | -## Will Message Behavior |
29 | | - |
30 | | -Authorization checks for durable sessions are now performed at the moment of client disconnection to determine whether the will message may be published. |
31 | | - |
32 | | -Previously, these checks were deferred until after the configured `Will-Delay-Interval` had expired. |
33 | | - |
34 | | -## Configuration Changes |
35 | | - |
36 | | -**Durable Sessions** |
37 | | - |
38 | | -- `durable_storage.messages.n_sites` parameter has been renamed to `durable_storage.n_sites`. This parameter has become common for all durable storage. |
39 | | -- `durable_storage.sessions` and `durable_storage.timers` have been added. |
40 | | -- [#15734](https://github.com/emqx/emqx/pull/15734) Improved the reliability and throughput of durable sessions. |
41 | | - |
42 | | -**Durable Storage** |
43 | | - |
44 | | -- `durable_storage.messages.n_sites` has been renamed to `durable_storage.n_sites`, which now applies to all durable storage types. |
45 | | -- Added new configuration entries for `durable_storage.sessions` and `durable_storage.timers`. |
46 | | - |
47 | | -**RocketMQ** |
48 | | - |
49 | | -- [#15635](https://github.com/emqx/emqx/pull/15635) The `parameters.strategy` field no longer accepts key templates (which previously implied the `key_dispatch` strategy). |
50 | | - Instead, set `parameters.strategy = key_dispatch` explicitly and specify the key template in `parameters.key`. |
51 | | - |
52 | | -**Platform Support** |
53 | | - |
54 | | -- [#15613](https://github.com/emqx/emqx/pull/15613) Discontinued package builds for Debian 10. |
55 | | - |
56 | | -## Rate Limit |
57 | | - |
58 | | -- [#15743](https://github.com/emqx/emqx/pull/15743) Listener connection rate limits (`max_conn_rate` and `max_conn_burst`) are now enforced per listener rather than per acceptor, restoring the behavior before 5.9.0. As a result, configurations from versions 5.9.0, 5.9.1, and 5.10.0 are incompatible: the specified rate values must be scaled up by the number of acceptors configured for each listener to preserve the same effective limits. |
| 7 | + If you relied on the previous (incorrect) behavior, you may need to update your payload templates to ensure messages are formatted as expected. |
0 commit comments