The ScyllaDB team announces ScyllaDB Enterprise 2022.2.6, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2022.2.
Related Links
- Get ScyllaDB Enterprise 2022.2.6 (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: Adding nodes to a large cluster (90+ nodes) may cause existing nodes to crash. The root cause is quadratic behavior in get_address_ranges function #12724
-
Stability: a very rare failure in a mutation validation failure test, when Materialized View building stops just as it reaches the end of the base table, deciding it needs to stop and also reset the reader to the start token at the same time while the compaction state also thinking the last read partition will be resumed. #12629
-
Tools: total disk space used metric incorrectly tells the amount of disk space ever used, which is wrong. It should tell the size of all SSTable being used plus the ones waiting to be deleted.
Live disk space used shouldn’t account for the ones waiting to be deleted, and live SSTable Count shouldn’t account SSTable waiting to be deleted. #12717 -
Stability: reader_concurrency_semaphore: inactive reader eviction is too aggressive, leading to Reads timing out, especially in range scans. #11803