[RELEASE] ScyllaDB 5.4.9

The ScyllaDB team announces ScyllaDB Open Source 5.4.9, a bugfix release of the ScyllaDB 5.4 stable branch. ScyllaDB Open Source 5.4.9, 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 6.0 and you are encouraged to upgrade to it.

Related links:

Issue fixed in this release:

  • Security: the new ScyllaDB image (GCP, AWS, Azure, Docker) includes a fix for OpenSSH Vulnerability CVE-2024-6387.
  • ADMIN API: Alternator, ScyllaDB’s Amazon DynamoDB compatible API, is using internal CQL tables under the hood. The (internal) names of Alternator Local Secondary Index (LSI) are not CQL standard, which breaks some of ScyllaDB REST API operations. #5883
  • ADMIN API: using the admin REST API may lead to a crash with assertion `!_end && !_zc_bufs && “Was this stream properly closed?”’ failed #19494
  • Stability: Batches (as generated by the BATCH statement) are held in the system.batchlog table. As this table can accumulate a lot of tombstones, we now take steps to ensure these tombstones are purged eagerly. This is important for repair, which replays the batch log. #19376
  • CQL: DESC does not report CQL Table Extensions#19334
  • Stability: init - Startup failed: std::runtime_error (Failed to mark node as alive in 30000 ms …). The root cause is a node booting in gossip topology waits until all NORMAL nodes are UP. If we removed a different node just before, the booting node could still see it as NORMAL and wait for it to be UP, which would time out and fail the bootstrap. #17526
  • Stability: nodetool repair command failed with exit code3 during drop keyspace #18490
  • Performance: The gossiped view update backlog is only read on shard 0 #19232
  • Performance: Statements such as SELECT count(*) use an internal map-reduce service to parallelize the query. ScyllaDB no longer does so for single-partition queries as they don’t benefit from it. #19349
  • Monitoring: ScyllaDB now enables per-table metrics by default on a per-instance level. Some of the metrics, like cache_hit_rate, latency and live_disk_space were not reported, and missing from the Monitoring Table Dashboard. #18642