The ScyllaDB team announces ScyllaDB Enterprise 2022.1.9, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.1.
Note that there is a newer Feature Enterprise release: ScyllaDB Enterprise 2022.2. While we will continue to support 2022.1 LTS, you can get additional features with 2022.2.
- Get ScyllaDB Enterprise 2022.1.9 (customers only, or 30-day evaluation)
- Upgrade from 2021.1.x to 2022.1.y
- Upgrade from ScyllaDB Open Source 5.0 to ScyllaDB 2022.1
- Submit a ticket
Below is a list of performance and stability improvements and bug fixes, each with an open-source reference if available:
- CQL Conflict resolution: compare_cells_for_merge may wrongly prefer an expired cell over a live and expiring one #14182. Before this fix, when two cells have the same write timestamp and both are alive or expiring, we compare their value first, before checking if either of them is expiring and if both are expiring, comparing their expiration time and TTL value to determine which of them will expire later or was written later. This was based on an early version of Cassandra. However, the Cassandra implementation rightfully changed in CASSANDRA-14592, where the cell expiration is considered before the cell value. See update-ordering in Scylla docs for more.
- Setup: perftune.py: Error on parsing CPU mask seastar#1179
- Setup: scylla-fstrim.timer is enabled but not started #14249
- Setup: The installer now wipes filesystem signatures from the individual disks making up a RAID array, preventing problems with reuse of disks. #13737
- Stability: compaction: excessive reallocation during input list formatting #14071. Issue is more likely with offstrategy compaction.
- Stability: deadlock caused by view update _registration_sem and streaming reader _streaming_concurrency_sem #14676