[RELEASE] ScyllaDB 5.1 RC2
Tzach Livyatan
<tzach@scylladb.com>The Scylla team is pleased to announce ScyllaDB Open Source 5.1 RC2, the second Release Candidate for the Scylla Open Source 5.1 minor release.
We encourage you to run ScyllaDB 5.1 release candidates on your test environments; this will help ensure that an upgrade to ScyllaDB 5.1 General Availability will proceed smoothly with your workload. Use the release candidate with caution; RC2 is not production-ready yet. You can help stabilize Scylla Open Source 5.1 by reporting bugs here.
Only the last two minor releases of the ScyllaDB Open Source project are supported. Once Scylla Open Source 5.1 is officially released, ScyllaDB Open Source 5.1 and 5.0 will be supported, and ScyllaDB 4.6 will be retired.
For a complete description of ScyllaDB 5.1 see ScyllaDB 5.1 RC1.
Related Links
* Get ScyllaDB Open Source 5.1 (under “More Versions” for each distro)
Updates and bug fixes since 5.1 RC1
Performance: Long-term index caching in the global cache, as introduced in 4.6, hurts the performance for workloads where accesses to the index are sparse. To mitigate this, a new configuration parameter cache_index_pages (default true) is introduced to control index caching. Setting the flag to `false` causes all index reads to behave like they would in BYPASS CACHE queries. Consider using false if you notice performance problems due to lowered cache hit ratio in 4.6 or 5.0. The config API can update the parameter live (without restart). Fix #11202
Stability: replica: evict all inactive reads for a table when dropping it #11264
Security: Undefined behavior in transport decompression code #11476. see ScyllaDB Security Advisory SDBA-2022-0001 (high severity).
Stability: following restart node continues to log INFO message “Commitlog shutdown complete" messages #11508
Stability: a combination of low memory condition and “--abort-on-seastar-bad-alloc” debug option and a reclaim stall can lead to Scylla crash #11549. This only affects QA workloads.