[RELEASE] ScyllaDB 5.2.17

The ScyllaDB team announces ScyllaDB Open Source 5.2.17, a bugfix release of the ScyllaDB 5.2 stable branch. ScyllaDB Open Source 5.2.17, 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:

Issue fixed in this release:

  • Alternator: some sstables with large sizes left after TTL expiration, gc-grace-period and major compaction (tombstones are not deleted). The root cause is sstable waiting for off-strategy compaction, not participating in the major compaction #11915.
  • Alternator: a bug in Alternator GSI updates of range key when using two new key columns in GSI #17119
  • Stability: Materialized View (MV) flow control doesn’t account small view updates properly, and can lead to OOM #17364
  • Stability: Materialized View (MV): memory used by a view updates batch is incorrectly divided #17854
  • Stability: nodetool removenode hangs in repair, waiting on streaming semaphore #17591
  • Stability: reader_permit::get_schema() is unsafe against table schema alter or drop #16180
  • Stability: wrong range used for partition estimation for mixed-shard repair, when different nodes have different shared counts, resulting in larger than needed filters #17863.
  • Stability: Sporadic repair failure when adding a node #16821
  • Stability: a very rare use-after-free in sstables::key_view::explode() can be caused by a large enough partition key #17625
  • Scylla AMI for EC2: Cannot get EC2 user data after enabled IMDSv2 scylla-machine-image#498