[RELEASE] ScyllaDB 5.1.5

Release Notes
, ,
1

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

Users are encouraged to upgrade to 5.1.5.

Related links:

Issue fixed in this release:

  • CQL: scylla: types: is_tuple(): doesn’t handle reverse types. For example, a schema with reversed clustering key component; this component will be incorrectly represented in the schema CQL dump: the UDT will lose the frozen attribute. When attempting to recreate this schema based on the dump, it will fail as the only frozen UDTs are allowed in primary key components.

#12576

  • Alternator Streaming API: unexpected ARN values by list streams paged responses. This issue may only affect users with many, more than 100, tables with streams #12601
  • Stability: ScyllaDB tracks transient memory used by queries. However, it did not track decompressed memory buffers, which could lead to running out of memory in some complicated queries. #12448
  • Stability: Cached reads may temporarily miss rows under rare conditions #12451
  • Stability: During startup, ScyllaDB makes sstables conform to the compaction strategy reshaping, so that future reads will perform well. It is now more careful when reshaping Leveled Compaction Strategy tables, to avoid doing unnecessary work and using too much disk space #12495.
  • Stability: prevent heap use-after-free of forward_aggregates in parallel aggregators #12528
  • Stability: crash in Materialized View update row locking, caused by a race condition #12632
  • Stability: commitlog: segment recycling breaks on segment file removal #12645
  • Stability: Crash when reporting error on invalid CQL query involving field selection from a user-defined type #12739
  • Docs: mixing compression and compaction in Data Definition page #12334