[RELEASE] ScyllaDB 5.4.4

Release Notes
, ,
1

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

Users are encouraged to upgrade to 5.4.4.

Related links:

Issue fixed in this release:

  • cdc: allow sending writes to the previous generation for some time after switching #7251. The previous bypass for this issue, retry the request, does not work when using LWT and CDC on the same table. The issue can appear both in CQL CDC and Alternator (Amazon DynamoDB compatible API) Streams.

  • Stability: streaming might fail when a table is dropped. Streaming can be part of a repair, topology change (adding/removing a node), etc. #15370, #17028, #15598

  • Stability: Having an index being dropped during the bootstrap causes a node to fail to start #15598

  • Stability: throughput_limits_test.TestCompactionLimitThroughput.test_can_limit_compaction_throughput is flakey #15721. The root cause is race conditions during server shutdown, between compaction and closing compaction_history table.

  • Stability: in rare cases, nodetool getsstables or calling REST API /column_family/sstables/by_key/ can crash the server #17232

  • Stability: query_tombstone_page_limit applies to unpaged queries, while it should not #17241

  • Stability: rare issue when table drop concurrent to any repair or streaming (so any node ops) #16899, #15425.

  • MV Correctness: in some cases, like one base table with many views, updates to MV might be lost. In one example range tombstones made the issue appears earlier #17117

  • Build: Regenerate frozen toolchain for gnutls 3.8.3 and clang clang-16.0.6-4. #17285

  • Build: update Rust dependencies pull#17407. Rust is used to test WASM, an experimental feature in 5.4