The ScyllaDB team announces ScyllaDB Enterprise 2024.1.4, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2024.1 LTS Release.
2024.1.4 patch release includes multiple minor bug fixes.
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: Tombstone GC is extremely ineffective when Memtable is frequently appended with old data #17599
- Stability: scylla start very slowly, spend a lot of time for Loading repair history. The root cause is repair load not done in the background #16774
- Stability: a rare race condition in gossiper causes nodes to fail observing updated application states of other nodes in gossiper. This as flaky tests, but not as far as we know in production, #15393, #15602, #16668, #16902, #17493, #18118
- Stability: database: view_update_generator is unplugged before writes are drained spamming the log when stopping it. #16001
- Stability: Drop bloom filters from memory, if their total memory consumption is above the configured limit. #17747
- Stability: Reclaimed bloom filter is left back in disk when the SSTable is deleted #18398
- Stability: Materialized View (MV) flow control doesn’t account small view updates properly, and can lead to OOM #17364
- Stability: Materialized View (MV): memory used by a view updates batch is incorrectly divided #17854
- Stability: MV semaphore units are not kept alive until a view update finishes #17890
- Tooling: native sstable validation yields false positive errors (limited to MX format) #16326
- Stability: nodetool removenode hangs in repair, waiting on streaming semaphore #17591
- Stability: Potential use-after-move in streaming’s stream_result_future (courtesy of clang-tidy) #18332
- Stability: reclaim_timer::report() is marked noexcept, but its implementation throws #18099
- Stability: repair: memory accounting does not include keys #16710
- Stability: The estimated_partitions is overestimated for repair #18140
- Stability: Use-after-move in sstable writer (courtesy of clang-tidy) #18323
- Stability: Use-after-move in thrift/handler.cc:make_non_overlapping_ranges() (courtesy of clang-tidy) #18356
- Tracing: Large partition/row/cell warnings should not print keys contents #18041