# \[RELEASE\] ScyllaDB Enterprise 2022.1.8

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2022-1-8/684>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2022-1\
**Created:** [July 11, 2023, 5:57pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-1-8/684 "2023-07-11T17:57:24Z")\
**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:** [July 11, 2023, 5:57pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-1-8/684/1 "2023-07-11T17:57:24Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2022.1.8, a bug-fix production-ready ScyllaDB Enterprise patch release for [ScyllaDB Enterprise 2022.1](https://www.scylladb.com/product/release-notes/scylladb-enterprise-release-2022-1-0/).

Note that there is a newer Feature Enterprise release: [ScyllaDB Enterprise 2022.2](https://forum.scylladb.com/t/scylladb-enterprise-release-2022-2-0/269). While we will continue to support 2022.1 LTS, you can get additional features with 2022.2.

Related Links

- [Get ScyllaDB Enterprise 2022.1.8](https://www.scylladb.com/download/#enterprise) (customers only, or 30-day evaluation)
- [Upgrade from 2021.1.x to 2022.1.y](https://docs.scylladb.com/stable/upgrade/upgrade-enterprise/upgrade-guide-from-2022.x.y-to-2022.x.z)
- [Upgrade from ScyllaDB Open Source 5.0 to ScyllaDB 2022.1](https://docs.scylladb.com/stable/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.0-to-2022.1)
- [Submit a ticket](https://supportscylladb.zendesk.com/hc/en-us/requests/new)

Below is a list of performance and stability improvements and bug fixes, each with an open-source reference if available:

- Stability: Range-scans have a protection against using the wrong service-level to continue a suspended range-scan. This protection had a mistake, resulting in the node crashing when the protection mechanism was triggered. multishard\_mutation\_query: reader\_context::lookup\_readers() is not exception safe w.r.t. closing readers [#13784](https://github.com/scylladb/scylladb/issues/13784)

- Performance: ScyllaDB uses an interval map data structure from the Boost library to quickly locate sstables needed to service a read. Due to the way we interface with the library, updating the interval map was unnecessarily slow. This is now [fixed](https://github.com/scylladb/scylladb/commit/169a8a66f282cb420197f446134c61760f1a087b). [#11669](https://github.com/scylladb/scylladb/issues/11669)

- Stability: All rpc::client objects have to be stopped before they are destroyed. Currently this is done in  
messaging\_service::shutdown(). The cql\_test\_env does not call shutdown() currently. This can lead to use-after-free, leading to sigsegv [#12244](https://github.com/scylladb/scylladb/issues/12244)

- Stability: race condition in gossip and failure detector [#10547](https://github.com/scylladb/scylladb/issues/10547)

- Stability: mutation\_reader\_merger can overflow stack when merging many empty readers. This may happen when running a second repair right after the other. [#14415](https://github.com/scylladb/scylladb/issues/14415)

- UX: Allow tombstone GC in compaction to be disabled on user request [#14077](https://github.com/scylladb/scylladb/issues/14077)  
The fix adds new APIs /column\_family/tombstone\_gc and /storage\_service/tombstone\_gc, that will allow for disabling tombstone garbage collection (GC) in compaction.