[RELEASE] ScyllaDB 5.2.12

Release Notes
, ,
1

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

  • Correctness: assigning position_in_partition is not exception safe, in a rare combination of heavy memory pressure and large read it may lead to incorrect data response #15822
  • Correctness: a rare combination of reconciliation (read repair) with reverse queries and range tombstones, could cause incorrect data to be returned from queries #10598
  • Correctness: Row cache updates do not provide strong exception safety guarantees. In a rare case, and when using CL=1, chache might return a stale value #15576
  • Build: docker upgrade all 3rd party packages on creation #16222
  • Stability: Exceptional future ignored in Task manager: seastar::gate_closed_exception #15211
  • Stability: maybe_fix_legacy_secondary_index_mv_schema() could reference dangling pointer #13720
  • Stability: Scylla cluster nodes utilize 100% of CPU even with no load #12774, #13377, #7753
  • Stability: reader_concurrency_semaphore: execution loop can stall #13540
  • Security: The WebAssembly runtime used to evaluate user defined functions (UDF) has been updated to address vulnerabilities. #13807 Note that UDF are experimental in 5.2
  • Stability: A regression in IPv6 address formatting, which caused nodetool problems, like breaking when there is an Alternator GSI in the database #16153, or cause a node to be stuck with “?U” status and Host ID is "null #16039
  • Stability: the sstable parser is now able to detect more types of corruption involving premature end-of-file with compressed sstables. #13599
  • Stability: Use statement might throw an exception instead of returning an exceptional future, for example if the keyspace is doesn’t exist #14449
  • UX: no appropriate error when AuthenticationFailed due to consistency level does not match(system_auth) #2339
  • Monitoring: Old version of node_exporter (1.6.1), updated to 1.7.0 #16085
  • Monitoring: metric name issue: scylla_database_reads_memory_consumption shows free memory for the system semaphore #13810