[RELEASE] ScyllaDB Enterprise 2024.1.18

Release Notes
, ,
1

The ScyllaDB team announces ScyllaDB Enterprise 2024.1.18, a bug-fix production-ready patch release for ScyllaDB Enterprise 2024.1 Long Term Support (LTS) Release.

Note there is a later, better, LTS (Long term Support) Release 2025.1, and you are encouraged to upgrade to it.

Moving an existing cluster to TLS without downtime

This release introduces a new Transitional state for node-node encryption.

The transitional state encrypts all outgoing traffic but allows non-encrypted incoming traffic, allowing an upgrade from non-encrypted to encrypted node-to-node traffic without downtime.

More here #18903

Related Links

Fixed Issue with an open-source reference:

Performance

  • Share IO queues between mountpoints seastar#2733 scylladb#23820

    Currently, Seastar assigns IO queues based on mountpoints listed in io-properties.yaml, mapping each mountpoint’s device number to an IO queue. However, this approach fails when a single physical disk is split into multiple virtual block devices with separate mountpoints, each gets its own IO queue, which is incorrect since they share the same underlying disk.

    This PR enhances the configuration format to allow a single disk entry to specify multiple mountpoints. Seastar will then create one IO queue for all specified mountpoints, correctly reflecting the shared physical disk.

  • compaction_manager::perform_task_on_all_files always executes a task, even if there are no sstables to compact #16803

  • chunked_managed_vector violates the preferred max contiguous allocation size #23854

  • clone semantics is incorrect for sstable runs in partitioned_sstable_set #17878

KMIP

ScyllaDB enables integration with external Key Management Interoperability Protocol (KMIP) servers for managing encryption keys, supporting Encryption at Rest.

  • Encryption at Rest: KMIP LOCATE operation request has incorrect attribute names #23970

    As a result the KMIP server rejected the request, leading ScyllaDB to assume that a key with
    these specifications doesn’t exist, and creates a new key in the KMIP server.