# \[RELEASE\] ScyllaDB Enterprise 2021.1.22

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2021-1-22/769>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2021-1\
**Created:** [August 8, 2023, 1:37pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2021-1-22/769 "2023-08-08T13:37:50Z")\
**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:** [August 8, 2023, 1:37pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2021-1-22/769/1 "2023-08-08T13:37:50Z")

</div>

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

ScyllaDB Enterprise [2022.1 LTS](https://www.scylladb.com/product/release-notes/scylladb-enterprise-release-2022-1-0/) is the latest Long-Term Support release, and [2022.2](https://forum.scylladb.com/t/scylladb-enterprise-release-2022-2-0/269) is the newest feature release. You are encouraged to upgrade in coordination with the ScyllaDB support team.

Related Links

- [Get ScyllaDB Enterprise 2021.1.22](https://www.scylladb.com/download/#enterprise) (customers only, or 30-day evaluation)
- [Upgrade from 2020.1.x to 2021.1.y](https://docs.scylladb.com/upgrade/upgrade-enterprise/upgrade-guide-from-2020.1-to-2021.1/)
- [Upgrade from ScyllaDB Open Source 4.3 to Scylla Enterprise 2021.1](https://docs.scylladb.com/upgrade/upgrade-to-enterprise/upgrade-guide-from-4.3-to-2021.1/)
- [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):

- CQL Conflict resolution: compare\_cells\_for\_merge may wrongly prefer an expired cell over a live and expiring one [#14182](https://github.com/scylladb/scylladb/issues/14182). Before this fix, when two cells have the same write timestamp and both are alive or expiring, we compare their value first, before checking if either of them is expiring and if both are expiring, comparing their expiration time and TTL value to determine which of them will expire later or was written later. This was based on an early version of Cassandra. However, the Cassandra implementation rightfully changed in [CASSANDRA-14592](https://github.com/scylladb/scylladb/pull/14651), where the cell expiration is considered before the cell value. See [update-ordering](https://opensource.docs.scylladb.com/master/cql/dml.html#update-ordering) in Scylla docs for more.
- Setup: scylla\_prepare: generating wrong perftune.yaml that could not run clocksource setting [#7672](https://github.com/scylladb/scylladb/issues/7672)
- Setup: scylla-fstrim.timer is enabled but not started [#14249](https://github.com/scylladb/scylladb/issues/14249)
- Setup: perftune.py: Error on parsing CPU mask [seastar#1179](https://github.com/scylladb/seastar/issues/1179)
- Setup: The installer now [wipes filesystem signatures](https://github.com/scylladb/scylladb/commit/fdceda20ccb3d15456d5b2af8582a01bd89e3aad) from the individual disks making up a RAID array, preventing problems with reuse of disks. [#13737](https://github.com/scylladb/scylladb/issues/13737)
- 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)