[RELEASE] ScyllaDB Enterprise 2024.1.7

Release Notes
, ,
1

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

Related Links

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

  • Security: the new ScyllaDB image (GCP, AWS, Azure, Docker) includes a fix for OpenSSH Vulnerability CVE-2024-6387.
  • Performance: in some cases, the I/O scheduler slows streaming even if the node is not exhausted with real time requests. Root cause is seastar/#1641
  • Performance: Internal access to the roles table was optimized #19299
  • 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
  • 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
  • Stability: chunked_vector::reserve_partial does not work as documented if size > max_chunk_capacity() #19254
  • 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
  • KMIP integration: Scylla wouldn’t start after setting up Hashicorp Vault as the KMIP server