The ScyllaDB team announces ScyllaDB Enterprise 2024.2.8, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2024.2 Feature (Short Term Support) Release.
Note there is a later LTS (Long term Support) Release 2025.1, and you are encouraged to upgrade to it.
Related Links
- Get ScyllaDB Enterprise 2024.2 (customers only, or 30-day evaluation)
- Upgrade Guide - ScyllaDB Enterprise 2024.1 to 2024.2
- Upgrade - ScyllaDB 6.0 to ScyllaDB Enterprise 2024.2
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
Correctness
- compacting_reader: decorated-key passed by reference to the compactor is moved. The compactor might use this moved-from key later to obtain tombstone GC information, which will result in incorrect tombstone GC decisions and possibly data resurrection. #23291
- Partitions are (temporarily) missing when combining range scans with SELECT DISTINCT or PER PARTITION LIMIT, and can result in omitting records from the table if they do read-repair. #20084
Stability:
-
Since Scylla 6.0, cache and memtable cells between 13 kiB and 128 kiB are getting allocated in the standard allocator rather than inside LSA segments. This can result in out of memory issue
#22941 #22389 #23781 -
compaction_manager::drain should wait if stop_ongoing_compactions is already in progress #20197
-
CDC: Race condition in handling of new generation during raft upgrade. new CDC generation from raft topology upgrade procedure not handled by every node; instead, legacy CDC code tries to obtain it (and fails) #21227
-
segfault when dumping semaphore diagnostics on SIGQUIT #22756
Debug
- Coredumps are not readable by gdb due to seastar memory prefaulter #23316
CQL