The ScyllaDB team announces ScyllaDB Enterprise 2024.1.11, a bug-fix production-ready patch release for ScyllaDB Enterprise 2024.1 LTS Release.
Related Links
- Get ScyllaDB Enterprise 2024.1 (customers only, or 30-day evaluation)
- Upgrade from ScyllaDB Enterprise 2023.1.x to 2024.1.y
- Upgrade from ScyllaDB Enterprise 2022.2.x to 2024.1.y
- Upgrade from ScyllaDB Open Source 5.4 to ScyllaDB Enterprise 2024.1.x
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
- Stability: waiting for counter update operations on table stop, result in Sudden Scylla shutdown - assert at cell_locker::~cell_locker #19980
- Stability: repair: dangling reference in insert_repair_meta #20057. May cause an issue in a race between repair and table drop.
- Stability(raft): shutdown phase can get stuck #19223 (found on repair testing)
- Stability: A crash in certain cases of schema changes while an sstable was being written was fixed. #16065
- Stability: system_keyspace update_peer_info and update_tokens called for the local endpoint #16425
- Stability: time_window_compaction_strategy::get_reshaping_job must limit partial_sort range to multi_window size. The result might be a crash and infinite restart loop #20608
- API: Alternator “/localnodes” request returns nodes which are still joining #19694
- Upgrade: Upgrade fails when the number of service levels close to the max. The root cause is ScyllaDB did not correctly identify internal scheduling groups, for example for maintenance, and tried to create service levels for them. #20070