# \[RELEASE\] ScyllaDB Enterprise 2024.1.17

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2024-1-17/4751>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2024-1\
**Created:** [April 20, 2025, 1:15pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-1-17/4751 "2025-04-20T13:15:05Z")\
**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:** [April 20, 2025, 1:15pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-1-17/4751/1 "2025-04-20T13:15:05Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2024.1.17, a bug-fix production-ready patch release for [ScyllaDB Enterprise 2024.1 Long Term Support (LTS) Release.](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-1-0/1292)

Note there is a later, better, 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.

### Related Links

- [Get ScyllaDB Enterprise 2024.1](https://www.scylladb.com/download/#enterprise) (customers only, or 30-day evaluation)
- [Upgrade from ScyllaDB Enterprise 2023.1.x to 2024.1.y](https://enterprise.docs.scylladb.com/branch-2024.1/upgrade/upgrade-enterprise/upgrade-guide-from-2023.1-to-2024.1/upgrade-guide-from-2023.1-to-2024.1-generic.html)
- [Upgrade from ScyllaDB Enterprise 2022.2.x to 2024.1.y](https://enterprise.docs.scylladb.com/branch-2024.1/upgrade/upgrade-enterprise/upgrade-guide-from-2022.2-to-2024.1/)
- [Upgrade from ScyllaDB Open Source 5.4 to ScyllaDB Enterprise 2024.1.x](https://opensource.docs.scylladb.com/stable/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.4-to-2024.1/index.html)
- [Submit a ticket](https://supportscylladb.zendesk.com/hc/en-us/requests/new)

## Fixed Issue with an open-source reference:

Correctness

- compacting\_reader: decorated-key passed by reference to the compactor is moved. The compactor might use this moved-from key later to obtain tombstone GC information, which will result in incorrect tombstone GC decisions and possibly data resurrection. [#23291](https://github.com/scylladb/scylladb/issues/23291)
- Partitions are (temporarily) missing when combining range scans with SELECT DISTINCT or PER PARTITION LIMIT, and can result in omitting records from the table if they do read-repair. [#20084](https://github.com/scylladb/scylladb/issues/20084)

## Stability

- compaction\_manager::drain should wait if stop\_ongoing\_compactions is already in progress [#20197](https://github.com/scylladb/scylladb/issues/20197)