[RELEASE] Scylla 5.0 RC3
Tzach Livyatan
<tzach@scylladb.com>The ScyllaDB team is pleased to announce Scylla Open Source 5.0 rc3, the second Release Candidate for the Scylla Open Source 5.0 major release.
Use the release candidate with caution; rc3 is not production-ready yet. You can help stabilize Scylla Open Source 5.0 by reporting bugs here.
Please note that only the last two minor releases of Scylla Open Source project are supported. Once Scylla Open Source 5.0 is officially released, only Scylla Open Source 5.0 and Scylla 4.6 will be supported, and Scylla 4.5 will be retired.
For a complete description of Scylla 5.0 new features and bug fixes, see Scylla 5.0 RC1.
Related Links
* Scylla 5.0 RC1 , RC2
* Get Scylla Open Source 5.0 (under “More Versions” for each distro)
Updates and bug fixes since 5.0 RC2
Docker: previous versions of Docker image run scylla as root. A regression introduced in 4.6 accidentally modified it to scylla user. #10261
Docker: Incompatible change of supervisor service name inside Scylla container image #10269
Docker: incorrect locale value in docker build script #10310
Docker: Scylla Docker doesn't have pidof, required by seastar-cpu-map.sh #10238
Fix a regression induce in 5.0rc0: range_tombstone_list: insert_from: incorrect range_tombstone applied to reverter in non-overlapping case #10326
CQL: Incorrect results returned with IN clause in a partition and index restriction and ALLOW FILTERING #10300
Stability: compare_atomic_cell_for_merge doesn't compare TTL if expiry is the same. This is not consistent with the way the cell hash is computed, and may cause repair to keep trying to repair discrepancies caused by the ttl being different. #10156, #10173
Stability: A crash in Scylla memory management code, triggered by index file caching, was fixed. The bug was caused by an allocation from within the memory allocator causing cache eviction in order to free memory. Freeing the evicted items re-enters the memory allocator, in a way that was not expected by the code. Fixes #9573
Stability: JSON formatter issues may cause API calls fail in some cases, for example top partition on a CDC table #9061
Seastar: Intensive mixed (e.g. compaction + query) IO could sporadically break through the configured limitations causing the disk to be overloaded which would result in increased IO latencies #10233