[RELEASE] ScyllaDB 5.2.11

The ScyllaDB team announces ScyllaDB Open Source 5.2.11, a bugfix release of the ScyllaDB 5.2 stable branch. ScyllaDB Open Source 5.2.11, like all past and future 5.x.y releases, is backward compatible and supports rolling upgrades.

Users are encouraged to upgrade to 5.2.11.

Related links:

Issue fixed in this release:

  • Stability: failure detector apis need to call gossiper on shard 0 #15816
  • Stability: migration_manager: schema version correctness depends on order of feature enabling #16004
  • Stability: nodetool enablebinary starts the CQL server in the streaming group, instead of statement group #15485
  • Stability: nodetool resetlocalschema should recalculate per-table schema digest #15380. With this change one can fix issues in Schema digest, like #4485, without a rolling restart.
  • Stability: Overloading scylla with materialized view writes can lead to deadlock #15844
  • Stability: ScyllaDB computes the version of the schema by hashing the mutations that describe the schema in the schema tables. This can lead to an inconsistency between nodes if tombstones are expired at different times. #4485
  • Stability: statements:describe: DESC FUNCTION <uda_name> and DESC AGGREGATE <udf_name> crashes Scylla #14360. Note that UDF/UDA are experimental in this release
  • Performance: High latency in Repair as part of RBNO bootstrap. In 5.2 RBNO is used by default for Replace node operation. #15505. The issue is a regression since 5.2.0.
  • Performance: Repairing a cluster after a restore causes severe reactor stalls throughout the cluster (due to expensive logging within do_repair_ranges() without yield) #14330
  • Install: scylla_post_install.sh: “[ $RHEL ]” does not work for RHEL, it only detects CentOS #16040
  • Tooling: update Java tooling, including new versions for
  • Tooling: [tools/scylla-sstable] more flexibility for obtaining the schema #10126. Root cause was the introducing of the Azure-snitch scylla-tools-java#338