[RELEASE] ScyllaDB 5.2.15

Release Notes
, ,
1

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

  • CQL: Server-side DESCRIBE should include scylladb-specific options like paxos_grace_seconds, and tombstone_gc #12389

  • Correctness: Inserted data only becomes available after restart. The root cause is a very rare bug in the cache, which is hidden (in most cases) by replication and reconciliation #16759. Thanks to user rngcntr for reporting and helping debug it.

  • Stability: Adding a column to the base table should invalidate prepared statements for views #16392

  • Stability: Bootstrap fails due to inconsistent schema after group0 catch up when table was recreated in the past, in an older version of Scylla #16683

  • Stability: database_test may fail due to ignored exceptional future on table drop #14971

  • Stability: nodes crashing during repair operations (due to no reader-closing on unexpected exception) #16606

  • Stability: Raft system storage needs to save the snapshot descriptor and truncate the log atomically. #9603 The original fix proved to be incomplete.

  • Stability: raft: large delays between io_fiber iterations in schema change test. #15622. ScyllaDB uses two separate memory reservation systems for memtables: user, used for user writes, and system, used for ScyllaDB’s own writes. The root cause was Raft did not use the system reservation.

  • Stability: Task manager api responds with Internal Server Error #14914

  • Stability: tasks: dangling reference to task’s child pointer #16380

  • Stability: When using Raft for topology and schema changes, ScyllaDB does not force the schema and topology to be transferred to new nodes. #14066

  • Stability: mintimeuuid() call with large negative timestamps may crash ScyllaDB. #17035

  • Setup: scylla_raid_setup: faillback to other paths when UUID not available #13803