The ScyllaDB team announces ScyllaDB Enterprise 2022.1.10, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.1.
Note that there is a newer Enterprise LTS release: ScyllaDB Enterprise 2023.1. While we will continue to support 2022.1 LTS, you can get additional features with 2023.1.
- Get ScyllaDB Enterprise 2022.1.10 (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:
- Logs: missing delimiter between partition key and clustering key in large data warning customer #11620
- Tooling: Incorrect sstablesPerRead values reflected in nodetool tablehistograms tools-java#330 #10089
- Performance: Compaction manager “periodic reevaluation” is one-off. This means that compaction was not kicking in later for a table, with low to none write activity, that had expired data 1 hour from now. #13430
- Performance: Compaction manager can cause reactor stalls during periodic submission #12390
- Performance: SSTable set is left uncompacted post off-strategy compaction completion, which may lead to suboptimal read and space amplification until the next compaction #13429
- Stability: partitioned_sstable_set::insert might stall when called by table::make_reader_v2_excluding_sstables. The root cause is View building from staging creates a reader from scratch for every partition, in order to calculate the diff between new staging data and data in base sstable set, and then pushes the result into the view replicas. #14244
- Stability: view_updating_consumer does not account for partition header size. In extreme case, this bug can cause OOM and exit when MV is created from a base table with many small partitions #14819