The ScyllaDB team announces ScyllaDB Open Source 5.2.2, a bugfix release of the ScyllaDB 5.2 stable branch. ScyllaDB Open Source 5.2.2, like all past and future 5.x.y releases, is backward compatible and supports rolling upgrades.
Users are encouraged to upgrade to 5.2.2.
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:
- Correctness: Decommission and removenode may lead to consistency issues if one of the nodes decides to abort during streaming #12989
- Correctness: tables with the new tombstone_gc ‘immediate’ mode delete all records when flushed to sstable #13572.
- Stability: ‘sleep_aborted’ error during Scylla shutdown #13374
- Stability: a rare failure in row_cache_test/test_concurrent_reads_and_eviction #12462
- Stability: a race condition in scylla boot, when migration_manager::sync_schema failed with seastar::rpc::closed_error causing repair to fail #12956, #12764
- Stability: Node operations failures get masked by abort request failures #12798
- Stability: Node operations may fail if prepare takes longer than heartbeat timeout #12969, #11011
- Stability: Segmentation fault happend on alive nodes during adding new node with replace terminated one #13368 (issues introduced in 5.2)
- Stability: Use-after-move in virtual table for secondary indexes #13396
- Stability: Use-after-move when initializing row cache with dummy entry #13400
- Stability: Use-after-move in virtual table for secondary indexes #13396
- Stability: Use-after-move when making streaming reader #13397
- Stability: Use-after-move when reading from SSTable in reverse #13394
- Stability: Use-after-move when tracking view builder progress #13395
- UX: non informative iotune warnings in scylla_kernel_check #13373