[RELEASE] ScyllaDB 5.1 RC5

[Tzach Livyatan]

The Scylla team is pleased to announce ScyllaDB Open Source 5.1 RC5, a 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; RC5 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. 

Related Links     

* ScyllaDB 5.1 RC1 , RC2, RC3, RC4

* Get ScyllaDB Open Source 5.1 (under “More Versions” for each distro) 

* Upgrade from ScyllaDB 5.0 to 5.1

* Report a problem

Updates and bug fixes since 5.1 RC4

• Stability on AWS EC2: From time to time Scylla reboot failed with “create *.Ec2Snitch: std::system_error (error system:110, Connection timed out)” error.  #10250

• Stability: Gossip now uses a better source to get live node information for truncate, reducing false failures of the TRUNCATE operation. #10296, #11928

• Docs: multiple relevant updates backported to 5.1 branch 

• Alternator: missing Projection field in return of DescribeTable #11470

• Stability: The view builder is responsible for building materialized views when a view is created and after repair. To control its memory consumption, it reads base table sstables in chunks. Due to a bug, it could forget the partition tombstone or an open range tombstone when moving between chunks, leading to a discrepancy between the base table data and the view data. This is now fixed. #11668

• Stability: Service Levels: Node crashes during parsing of service level creation with unreserved keywords #11774

Regards

Tzach