The ScyllaDB team announces ScyllaDB Open Source 5.1.13, a bugfix release of the ScyllaDB 5.1 stable branch. ScyllaDB Open Source 5.1.13, like all past and future 5.x.y releases are backward compatible and support rolling upgrades.
Note that the latest stable ScyllaDB Open Source release is 5.2, and you are encouraged to upgrade to it.
Related links:
- ScyllaDB Open Source 5.1
- 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.0.x to 5.1.y
- Please let us know if you encounter an issue.
Issue fixed in this release:
-
Stability: a lot of lsa-timing log messages during node replace cause c-s stuck and aborted. The fix update the reactor shares for default IO class from 1 to 200 #13753
-
Stability: ALTER KEYSPACE can break tables with UDT columns #14139
-
Stability: All rpc::client objects have to be stopped before they are destroyed. Currently this is done in messaging_service::shutdown(). The cql_test_env does not call shutdown() currently. This can lead to use-after-free, leading to sigsegv #12244
-
Stability: Level compaction is not working in cleanup #14035 (introduced in 5.1)
-
Stability: Range-scans have a protection against using the wrong service-level to continue a suspended range-scan. This protection had a mistake, resulting in the node crashing when the protection mechanism was triggered. multishard_mutation_query: reader_context::lookup_readers() is not exception safe w.r.t. closing readers #13784
-
Stability: Shutting down auth service may hang #13545