The ScyllaDB team announces ScyllaDB Enterprise 2023.1.8, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2023.1 LTS Release.
2023.1.8 patch release includes multiple minor bug fixes.
ScyllaDB Enterprise’s latest Long Term Support (LTS) is 2024.1. While we continue to support 2023.1, you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.
Related Links
- Get ScyllaDB Enterprise 2023.1 (customers only, or 30-day evaluation)
- Upgrade from ScyllaDB Enterprise 2022.1.x to 2023.1.y
- Upgrade from ScyllaDB Open Source 5.2 to ScyllaDB Enterprise 2023.1.x
- Upgrade from ScyllaDB Enterprise 2023.1.x to 2023.1.y
- Upgrade from ScyllaDB Enterprise 2023.1.x to 2024.1.y
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
- Alternator: some sstables with large sizes left after TTL expiration, gc-grace-period and major compaction (tombstones are not deleted). The root cause is sstable waiting for off-strategy compaction, not participating in the major compaction #11915.
- Stability: Tombstone GC is extremely ineffective when Memtable is frequently appended with old data #17599
- 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
- Tracing: Large partition/row/cell warnings should not print keys contents #18041
- 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
- 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: wrong range used for partition estimation for mixed-shard repair, when different nodes have different shared counts, resulting in larger than needed filters #17863.
- Stability: The estimated_partitions is overestimated for repair #18140
- Stability: Use-after-move in thrift/handler.cc:make_non_overlapping_ranges() (courtesy of clang-tidy) #18356
- Stability: Wrong exception is printed in build step exception handling #18423