The ScyllaDB team announces ScyllaDB Enterprise 2022.2.17, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.2 Feature Release.
Note the latest ScyllaDB Enterprise release is 2023.1 LTS, and very soon 2024.1 LTS, and you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.
- Get ScyllaDB Enterprise 2022.2.17 (customers only, or 30-day evaluation)
- Upgrade from 2022.1.x to 2022.2.y
- Upgrade from ScyllaDB Open Source 5.1 to ScyllaDB 2022.2
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
- Stability: ICS is incorrectly calculating GC before on its own, without taking into account the GC mode and other factors. This might lead to ICS wrongly assuming data can be GCed, but then compaction down the road realizes the data cannot be GCed
- Stability: ICS is making wrong decisions by not taking into account the GC mode and other factors. This might lead to ICS wrongly assuming data can be GCed, but then compaction down the road realizes the data cannot be GCed.
- Stability ICS does not respect tombstone interval condition for sstable runs possibly shadowing data in memtable
- Stability: ICS cross-tier tombstone compaction can be delayed indefinitely and doesn’t respect ‘tombstone_compaction_interval’
- Stability: ICS is not honoring tombstone GC mode when scheduling compaction jobs
- Correctness: assigning position_in_partition is not exception safe, in a rare combination of heavy memory pressure and large read it may lead to incorrect data response #15822
- Performance: Bloom filter efficiency can be reduced after node operation. When writing an sstable, ScyllaDB estimates how many partitions it will have in order to size the bloom filter correctly. In some cases, the estimation was suboptimal for TWCS. #15704
- Java Tools: Old version of libthrift, logback, Netty and others dependency scylla-tools-java#352, scylla-tools-java#364, scylla-tools-java#363