The ScyllaDB team announces ScyllaDB Open Source 5.2.16, a bugfix release of the ScyllaDB 5.2 stable branch. ScyllaDB Open Source 5.2.16, like all past and future 5.x.y releases, is backward compatible, and supports rolling upgrades.
Note that the latest ScyllaDB Open Source stable release is 5.4 and you are encouraged to upgrade to it.
Related links:
- ScyllaDB Open Source 5.2
- 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.1.x to 5.2.y
- Please let us know if you encounter an issue.
Issue fixed in this release:
-
cdc: allow sending writes to the previous generation for some time after switching #7251, #15260
The previous bypass for this issue, retry the request, does not work when using LWT and CDC on the same table. The issue can appear both in CQL CDC and Alternator (Amazon DynamoDB compatible API) Streams. -
Stability: streaming might fail when a table is dropped. Streaming can be part of a repair, topology change (adding/removing a node), etc. #15370, #17028, #15598
-
Stability: in rare cases, nodetool getsstables or calling REST API /column_family/sstables/by_key/ can crash the server #17232
-
Stability: query_tombstone_page_limit applies to unpaged queries, while it should not #17241
-
MV Correctness: in some cases, like one base table with many views, updates to MV might be lost. In one example range tombstones made the issue appears earlier #17117
-
Log: schema::describe: print
synchronous_updatesonly when it’s present in extension map #14924 -
Build: Regenerate frozen toolchain for gnutls 3.8.3 and clang clang-16.0.6-4. #17285