The ScyllaDB team announces ScyllaDB Open Source 5.2.19, a bugfix release of the ScyllaDB 5.2 stable branch. ScyllaDB Open Source 5.2.19, like all past and future 5.x.y releases, is backward compatible, and supports rolling upgrades.
Note that the latest ScyllaDB Open Source stable release is 6.0, and you are encouraged to upgrade to it. This is Scylla 5.2’s last patch release. Scylla 5.2 is no longer supported.
Related links:
- ScyllaDB Open Source 5.2
- 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 5.1.x to 5.2.y
- Please let us know if you encounter an issue.
Issue fixed in this release:
- Stability: Bad estimation for temporary sstables (containing GCed data only) causes, in the worst case, of 2x space amplification for filters #18283
- Stability: direct failure detector: make ping timeout configurable and increase the default, from 300 to 600 ms #16607. Failure detector is an internal inter-node mechanism.
- Stability: Potential use-after-move in streaming’s stream_result_future (courtesy of clang-tidy) #18332
- Stability: Reclaimed bloom filter is left back in disk when the SSTable is deleted #18398
- Stability: Use-after-move in thrift/handler.cc:make_non_overlapping_ranges() (courtesy of clang-tidy) #18356
- Stability: Wrong exception is printed in build step exception handling #18423