ScyllaDB 5.1 release candidate

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

Updates and bug fixes since 5.1 RC3

  • Alternator: UpdateItem setting the same value again for GSI range key may drop the row #11801
  • Alternator: DescribeTable calls should include ProvisionedThroughput. Note that after the fix the returned ProvisionedThroughput is always zero, as Alternator does not support provisioned throughput #11222

Stability: Memtable flush aborts the node if it fails due to out-of storage space #11245

2 Likes

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

Updates and bug fixes since 5.1 RC3

  • Alternator: UpdateItem setting the same value again for GSI range key may drop the row #11801
  • Alternator: DescribeTable calls should include ProvisionedThroughput. Note that after the fix the returned ProvisionedThroughput is always zero, as Alternator does not support provisioned throughput #11222
  • Stability: Memtable flush aborts the node if it fails due to out-of storage space #11245

Regards

Tzach

1 Like

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

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