# \[RELEASE\] ScyllaDB Enterprise 2024.2.10

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2024-2-10/4894>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2024-2\
**Created:** [June 9, 2025, 8:01am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-2-10/4894 "2025-06-09T08:01:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tzach](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tzach/32/172_2.png) [@tzach](https://forum.scylladb.com/u/tzach)\
**Post date:** [June 9, 2025, 8:01am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-2-10/4894/1 "2025-06-09T08:01:42Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2024.2.10, a bug-fix production-ready ScyllaDB Enterprise patch release for [ScyllaDB Enterprise 2024.2 Feature (Short Term Support) Release.](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-2-0/3210)

Note there is a later LTS (Long term Support) [Release 2025.1](https://forum.scylladb.com/t/release-scylladb-2025-1/4692/3), 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](https://docs.scylladb.com/manual/master/operating-scylla/security/node-node-encryption.html).

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](https://docs.scylladb.com/manual/master/operating-scylla/security/node-node-encryption.html#moving-an-existing-cluster-to-tls-without-downtime) [#18903](https://github.com/scylladb/scylladb/issues/18903)

Related Links

- [Get ScyllaDB Enterprise 2024.2](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-2-0/3210) (customers only, or 30-day evaluation)
- [Upgrade Guide - ScyllaDB Enterprise 2024.1 to 2024.2](https://enterprise.docs.scylladb.com/branch-2024.2/upgrade/upgrade-enterprise/upgrade-guide-from-2024.1-to-2024.2/upgrade-guide-from-2024.1-to-2024.2-generic.html)
- [Upgrade - ScyllaDB 6.0 to ScyllaDB Enterprise 2024.2](https://enterprise.docs.scylladb.com/branch-2024.2/upgrade/upgrade-enterprise/upgrade-guide-from-2024.1-to-2024.2/upgrade-guide-from-2024.1-to-2024.2-generic.html)
- [Submit a ticket](https://supportscylladb.zendesk.com/hc/en-us/requests/new)

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

Stability

- Better handling of errors and expectations in [Encryption at Rest](https://enterprise.docs.scylladb.com/branch-2024.2/operating-scylla/security/encryption-at-rest.html) (EaR) [#19753](https://github.com/scylladb/scylladb/issues/19753) [#19960](https://github.com/scylladb/scylladb/issues/19960)

Tablets

- Fix the message when creating a new Tablet Keyspace [#24006](https://github.com/scylladb/scylladb/issues/24006)

Monitoring

- node\_ops\_finished\_percentage metric for removenode with RBNO never reaching 1, even though removenode finishes [#21174](https://github.com/scylladb/scylladb/issues/21174)

Tooling

- scylla-nodetool: status: negative load size crashes nodetool [#24134](https://github.com/scylladb/scylladb/issues/24134)

Config

- Fix description of commitlog\_use\_hard\_size\_limit [#23780](https://github.com/scylladb/scylladb/issues/23780)

Performance

- Share IO queues between mountpoints [seastar#2733](https://github.com/scylladb/seastar/issues/2733) [scylladb#23820](https://github.com/scylladb/scylladb/issues/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.