# \[RELEASE\] ScyllaDB Enterprise 2023.1.7

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2023-1-7/1455>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2023-1\
**Created:** [April 4, 2024, 5:31pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2023-1-7/1455 "2024-04-04T17:31:17Z")\
**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 4, 2024, 5:31pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2023-1-7/1455/1 "2024-04-04T17:31:18Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2023.1.7, a bug-fix production-ready ScyllaDB Enterprise patch release for [ScyllaDB Enterprise 2023.1 LTS Release.](https://forum.scylladb.com/t/scylladb-enterprise-release-2023-1-0-part-1/792)

2023.1.7 patch release includes multiple minor bug fixes.

ScyllaDB Enterprise’s latest Long Term Support (LTS) is [2024.1](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-1-0/1292). While we continue to support 2023.1, you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.

Related Links

- [Get ScyllaDB Enterprise 2023.1](https://www.scylladb.com/download/#enterprise) (customers only, or 30-day evaluation)
- [Upgrade from ScyllaDB Enterprise 2022.1.x to 2023.1.y](https://enterprise.docs.scylladb.com/branch-2023.1/upgrade/upgrade-enterprise/upgrade-guide-from-2022.x-to-2023.1/upgrade-guide-from-2022.x-to-2023.1-generic.html)
- [Upgrade from ScyllaDB Open Source 5.2 to ScyllaDB Enterprise 2023.1.x](https://enterprise.docs.scylladb.com/branch-2023.1/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.2-to-2023.1/index.html)
- [Upgrade from ScyllaDB Enterprise 2023.1.x to 2023.1.y](https://enterprise.docs.scylladb.com/branch-2023.1/upgrade/upgrade-enterprise/upgrade-guide-from-2023.x.y-to-2023.x.z/upgrade-guide-from-2023.x.y-to-2023.x.z-generic.html)
- [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/index.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: frozen\_mutation::unfreeze() stall in schema\_tables.cc: calculate\_schema\_digest. The issue (stalls) manifest on cluster with a large schema [#17841](https://github.com/scylladb/scylladb/issues/17841)
- Stability: a theoretical race when reading encryption\_file\_io\_extension may lead to undefined behavior.
- Stability: streaming might fail when a table is dropped. Streaming can be part of a repair, topology change (adding/removing a node), etc. [#15370](https://github.com/scylladb/scylladb/issues/15370), [#17028](https://github.com/scylladb/scylladb/issues/17028), [#15598](https://github.com/scylladb/scylladb/issues/15598)
- Stability: nodetool removenode hangs in repair, waiting on streaming semaphore [#17591](https://github.com/scylladb/scylladb/issues/17591)
- Stability: reader\_permit::get\_schema() is unsafe against table schema alter or drop [#16180](https://github.com/scylladb/scylladb/issues/16180)
- Stability: Sporadic repair failure when adding a node [#16821](https://github.com/scylladb/scylladb/issues/16821)
- Stability: a very rare use-after-free in sstables::key\_view::explode() can be caused by a large enough partition key [#17625](https://github.com/scylladb/scylladb/issues/17625)
- Stability: fair\_queue: Do not pop unplugged class immediately. The issue can manifest with a crash during cleanup: [seastar/src/core/fair\_queue.cc:222: void seastar::fair\_queue::pop\_priority\_class [seastar#eb093f8](https://github.com/scylladb/scylla-enterprise-seastar/commit/eb093f8a3a6424b75fd306c0c6d82fa18678b4bd)
- Set up: iotune doesn’t close files that weren’t correctly opened, for example when test directory creation failed for whatever reason, leading to iotune crash. [seastar#b9fd21d](https://github.com/scylladb/scylla-enterprise-seastar/commit/b9fd21d888d16f337c4134d558e835d9aaf47d70)
- Alternator: a bug in Alternator GSI updates of range key when using two new key columns in GSI [#17119](https://github.com/scylladb/scylladb/issues/17119)
- Scylla AMI for EC2: Cannot get EC2 user data after enabled IMDSv2 [scylla-machine-image#498](https://github.com/scylladb/scylla-machine-image/issues/498)