# \[RELEASE\] ScyllaDB Enterprise 2023.1.8

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2023-1-8/1988>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2023-1\
**Created:** [May 10, 2024, 8:18am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2023-1-8/1988 "2024-05-10T08:18:59Z")\
**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:** [May 10, 2024, 8:18am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2023-1-8/1988/1 "2024-05-10T08:18:59Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2023.1.8, 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.8 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):

- Alternator: some sstables with large sizes left after TTL expiration, gc-grace-period and major compaction (tombstones are not deleted). The root cause is sstable waiting for off-strategy compaction, not participating in the major compaction [#11915](https://github.com/scylladb/scylladb/issues/11915).
- Stability: Tombstone GC is extremely ineffective when Memtable is frequently appended with old data [#17599](https://github.com/scylladb/scylladb/issues/17599)
- Stability: Drop bloom filters from memory, if their total memory consumption is above the configured limit. [#17747](https://github.com/scylladb/scylladb/issues/17747)
- Stability: Reclaimed bloom filter is left back in disk when the SSTable is deleted [#18398](https://github.com/scylladb/scylladb/issues/18398)
- Tracing: Large partition/row/cell warnings should not print keys contents [#18041](https://github.com/scylladb/scylladb/issues/18041)
- Stability: Materialized View (MV) flow control doesn’t account small view updates properly, and can lead to OOM [#17364](https://github.com/scylladb/scylladb/issues/17364)
- Stability: Materialized View (MV): memory used by a view updates batch is incorrectly divided [#17854](https://github.com/scylladb/scylladb/issues/17854)
- Stability: MV semaphore units are not kept alive until a view update finishes [#17890](https://github.com/scylladb/scylladb/issues/17890)
- Stability: Potential use-after-move in streaming’s stream\_result\_future (courtesy of clang-tidy) [#18332](https://github.com/scylladb/scylladb/issues/18332)
- Stability: reclaim\_timer::report() is marked noexcept, but its implementation throws [#18099](https://github.com/scylladb/scylladb/issues/18099)
- Stability: repair: memory accounting does not include keys [#16710](https://github.com/scylladb/scylladb/issues/16710)
- Stability: wrong range used for partition estimation for mixed-shard repair, when different nodes have different shared counts, resulting in larger than needed filters [#17863](https://github.com/scylladb/scylladb/issues/17863).
- Stability: The estimated\_partitions is overestimated for repair [#18140](https://github.com/scylladb/scylladb/issues/18140)
- Stability: Use-after-move in thrift/handler.cc:make\_non\_overlapping\_ranges() (courtesy of clang-tidy) [#18356](https://github.com/scylladb/scylladb/issues/18356)
- Stability: Wrong exception is printed in build step exception handling [#18423](https://github.com/scylladb/scylladb/issues/18423)