# \[RELEASE\] ScyllaDB Enterprise 2022.2.18

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-18/1303>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2022-2\
**Created:** [February 14, 2024, 2:50pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-18/1303 "2024-02-14T14:50:36Z")\
**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:** [February 14, 2024, 2:50pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-18/1303/1 "2024-02-14T14:50:36Z")

</div>

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

Note the latest ScyllaDB Enterprise release is [2024.1 LTS](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-1-0/1292), and you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.

Related Links

- [Get ScyllaDB Enterprise 2022.2.18](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 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.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 issues are fixed in this release (with an open-source reference, if available):

- Correctness: Inserted data only becomes available after restart. The root cause is a very rare bug in the cache, which is hidden (in most cases) by replication and reconciliation [#16759](https://github.com/scylladb/scylladb/issues/16759).
- Stability: a rare case in which after a node restart, during a short window of time, [workload prioritizations](https://enterprise.docs.scylladb.com/stable/using-scylla/workload-prioritization.html)are not yet propagated to the node, a node can assume wrong priorities, and crash with OOM.
- Stability: Use statement might throw an exception instead of returning an exceptional future, for example, if the keyspace doesn’t exist [#14449](https://github.com/scylladb/scylladb/issues/14449)
- Setup: scylla\_raid\_setup fails when disk UUID is not available [#13803](https://github.com/scylladb/scylladb/pull/13803)