The ScyllaDB team announces ScyllaDB Open Source 5.0.13, a bugfix release of the ScyllaDB 5.0 stable branch. Like all past and future 5.x.y releases, it is backward compatible and supports rolling upgrades.
Note that the latest stable branch of ScyllaDB is 5.2.
ScyllaDB 5.0 branch is no longer supported, and this is the last patch release on this branch.
Related links:
- ScyllaDB Open Source 5.0
- Get ScyllaDB Open Source - AWS AMI, GCP Docker, binary packages and unified installer
- ScyllaDB Web Installer for Linux (all releases)
- Upgrade from ScyllaDB Open Source 5.x.y to Scylla Open Source 5.x.z
- Upgrade from ScyllaDB Open Source 4.6.x to 5.0.y
- Please let us know if you encounter an issue.
Issues fixed in this release:
-
Stability: distributed_loader should first detect the highest generation in a table before allowing new sstables to be created in it #11793. This is a root cause for: View building fail to move staging SSTables to base dir because generations are taken #11789
-
Stability: reader_concurrency_semaphore: inactive reader eviction is too aggressive, leading to Reads timing out, especially in range scans. #11803
-
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: 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