[RELEASE] ScyllaDB Enterprise 2023.1.5

Release Notes
, ,
1

The ScyllaDB team announces ScyllaDB Enterprise 2023.1.5, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2023.1 LTS Release.

2023.1.5 patch release includes multiple minor bug fixes.

ScyllaDB Enterprise’s latest Long Term Support (LTS) is 2024.1. While we continue to support 2023.1, you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.

Related Links

The following issues are fixed in this release (with an open-source reference, if available):

  • 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.
  • Stability: a rare case in which after a node restart, during a short window of time, workload prioritizations are not yet propagated to the node, a node can assume wrong priorities, and crash with OOM.
  • Stability: Adding a column to the base table should invalidate prepared statements for views #16392
  • Stability: Bootstrap fails due to inconsistent schema after raft 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
  • 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
  • Tools: scylla-sstable: tool failed on deprecated configuration, while scylla itself doesn’t #16538
  • Setup: scylla_raid_setup: faillback to other paths when UUID not available #13803