# \[RELEASE\] ScyllaDB Enterprise 2022.2.11

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-11/707>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2022-2\
**Created:** [July 19, 2023, 12:23pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-11/707 "2023-07-19T12:23:55Z")\
**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 19, 2023, 12:23pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-11/707/1 "2023-07-19T12:23:55Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2022.2.11, a bug-fix production-ready ScyllaDB Enterprise patch release for [ScyllaDB Enterprise 2022.2](https://forum.scylladb.com/t/scylladb-enterprise-release-2022-2-0/269).

Related Links

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

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

- Stability: a rare failure in row\_cache\_test/test\_concurrent\_reads\_and\_eviction [#12462](https://github.com/scylladb/scylladb/issues/12462)

- Stability: a lot of lsa-timing log messages during node replace cause c-s stuck and aborted. The fix update the reactor shares for default IO class from 1 to 200 [#13753](https://github.com/scylladb/scylladb/issues/13753)

- 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: ICS compaction is not working in cleanup [#14035](https://github.com/scylladb/scylladb/issues/14035) (introduced in 2022.2.0)

- 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)

- Stability: bad\_alloc (seastar - Failed to allocate 536870912 bytes) [#13491](https://github.com/scylladb/scylladb/issues/13491). Root cause is a logic fault causing the reader to attempt to read all the data, consuming all memory. Can occur during sstableloader/nodetool refresh, repair or range scan.