The ScyllaDB team announces ScyllaDB Enterprise 2024.2.11, a bug-fix production-ready ScyllaDB Enterprise patch release for ScyllaDB Enterprise 2024.2 Feature (Short Term Support) Release.
Note there is a later LTS (Long term Support) Release 2025.1, and you are encouraged to upgrade to it.
Related Links
- Get ScyllaDB Enterprise 2024.2 (customers only, or 30-day evaluation)
- Upgrade Guide - ScyllaDB Enterprise 2024.1 to 2024.2
- Upgrade - ScyllaDB 6.0 to ScyllaDB Enterprise 2024.2
- Submit a ticket
The following issues are fixed in this release (with an open-source reference, if available):
Stability
- A rare race condition may cause assertion `_u.st == state::future’ failed. (reader concurrency semaphore related) #22919
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.
- User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions #23218 (match Apache Cassandra CVE-2025-23015)
Performance
- chunked_managed_vector violates the preferred max contiguous allocation size #23854