# \[RELEASE\] ScyllaDB Enterprise 2022.1.4 **URL:** \ **Category:** Release Notes\ **Tags:** enterprise, enterprise-release, enterprise-2022-1\ **Created:** [January 8, 2023, 12:09pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-1-4/241 "2023-01-08T12:09:33Z")\ **Posts on this page:** 2\ **Page:** 1
**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:** [January 8, 2023, 12:09pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-1-4/241/1 "2023-01-08T12:09:34Z")
The ScyllaDB team announces ScyllaDB Enterprise 2022.1.4, 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/). Related Links - [Get ScyllaDB Enterprise 2022.1.4](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: - Incremental Compaction Strategy ([ICS](https://docs.scylladb.com/stable/architecture/compaction/compaction-strategies.html#incremental-compaction-strategy-ics)) improvements and bug fixes: - Make ICS reshape more efficient for off-strategy compaction, including large data sets. This fix a regression in replace node operation, which uses Repair Base Node Operation ([RBNO](https://docs.scylladb.com/stable/operating-scylla/procedures/cluster-management/repair-based-node-operation.html)) - Crash on compaction completion when ICS ends up with a run containing staging and non-staging files. Error log: “scylla: sstables/sstables.cc:2744: - Workload Prioritization improvements and bug fix: - Stability: removing a service level during an sstable load could lead to reading deleted memory and exit - Stability: some requests can ‘leak’ into the default service level just after authentication - Stability: a bug in the service level controller, might give the wrong priority to a task, resulting in timeouts. - Stability: Long-term index caching in the global cache, as introduced in 4.6, is a major pessimization for workloads where accesses to the index are sparse. This release disables index caching by default, and provides a configuration parameter “cache\_index\_pages” to enable it [#11889](https://github.com/scylladb/scylladb/issues/11889) - CQL: Other restrictions ignored when clustering key is constrained [#6200](https://github.com/scylladb/scylla/issues/6200) [#12014](https://github.com/scylladb/scylladb/issues/12014) - Stability: segmentation fault in cases where the base table schema change while MV schema is cached [#10026](https://github.com/scylladb/scylla/issues/10026), [#11542](https://github.com/scylladb/scylladb/issues/11542) - Stability: Undefined behavior during repair in repair\_reader::make\_reader [#10882](https://github.com/scylladb/scylla/issues/10882) - Stability: The view builder is responsible for building materialized views when a view is created and after repair. To control its memory consumption, it reads base table sstables in chunks. Due to a bug, it could forget the partition tombstone or an open range tombstone when moving between chunks, leading to a discrepancy between the base table data and the view data. This is now [fixed](https://github.com/scylladb/scylladb/commit/5621cdd7f97850c22a3b026e4928dbde8e3d302e). [#11668](https://github.com/scylladb/scylladb/issues/11668) - Stability: unpop partition header of spent partition in multishard mutation query. With the fix, Scylla does not resume an already exhausted partition at the start of generating a new page. [#9482](https://github.com/scylladb/scylladb/issues/9482) - Alternator: wrong IS NOT NULL condition for GSI range key [#11800](https://github.com/scylladb/scylladb/issues/11800) - Stability: LWT insert crash if clustering key is null [#11954](https://github.com/scylladb/scylladb/issues/11954) - Stability: use-after-free in db/view row\_locker [#12168](https://github.com/scylladb/scylladb/issues/12168) - Stability: a possible race after successful authentication may lead to queries asynchronously queued with the wrong workload prioritization. [#12202](https://github.com/scylladb/scylladb/pull/12202) - Alternator: backport Alternator TTL patches from open source to 2022.1: - [scylladb/scylladb@c262309](https://github.com/scylladb/scylladb/commit/c26230943b882f2d3e0654345043ef507e280c5b): alternator TTL: add metrics - [scylladb/scylladb@db7b11c](https://github.com/scylladb/scylladb/commit/db7b11cfc49145fc4f84427d6b28c517f842f811): alternator: make TTL expiration scanner bypass cache - [scylladb/scylladb@e06b5d9](https://github.com/scylladb/scylladb/commit/e06b5d9306446a4956feec9dd6d7a80f51866388): alternator: updated compatibility.md about TTL feature - [scylladb/scylladb@49a8164](https://github.com/scylladb/scylladb/commit/49a8164fb7e6741049e7417c3d446558192f61e6): alternator: add configurable scan period to TTL expiration - Alternator: don’t allow LSI and GSI to use the same name [#10789](https://github.com/scylladb/scylladb/issues/10789) - Alternator: DescribeTable calls should include ProvisionedThroughput [#11222](https://github.com/scylladb/scylla/issues/11222) - Alternator: UpdateItem setting the same value again for GSI range key may drop the row [#11801](https://github.com/scylladb/scylladb/issues/11801) - Alternator: missing Projection field in return of DescribeTable [#11470](https://github.com/scylladb/scylladb/issues/11470) - API: Attempt to update the live-updatable option in `system.config` with wrong value produces the error `bad_lexical_cast` in the log [#10394](https://github.com/scylladb/scylla/issues/10394). Config in Scylla is represented as a virtual table, and can be updated (for a subset of parameters) using CQL. - CQL: fromJson() should accept “true” and “false” also as strings, as Apache Cassandra does. [#7915](https://github.com/scylladb/scylla/issues/7915) - CQL: scylla: materialized view doesn’t work if there is a “to” column [#9450](https://github.com/scylladb/scylla/issues/9450) - sstables::delete\_atomically(std::vector\)::\: Assertion `sstdir == sst-\>get\_dir()’ failed.” - Stability: Flat mutation reader functions such as upgrade\_to\_v2 are not exception safe and can cause crashes [#9065](https://github.com/scylladb/scylla/issues/9065) - Stability on AWS EC2: From time to time Scylla reboot failed with “create \*.Ec2Snitch: std::system\_error (error system:110, Connection timed out)” error. [#10250](https://github.com/scylladb/scylladb/issues/10250) - Stability: a concurrent DROP TABLE while streaming data to another node is now [tolerated](https://github.com/scylladb/scylla/commit/953af382813e4a71f2dc8a097f58e11c80509ee9). Previously, streaming would fail, requiring a restart of the node add or decommission operation. [#10395](https://github.com/scylladb/scylla/issues/10395) - Stability: Nodetool SCRUB failing when running on keyspaces with mv, indexes and auto snapshot enabled [#10760](https://github.com/scylladb/scylladb/issues/10760) - Stability: Nodetool SCRUB failing when running on keyspaces with mv, indexes and auto snapshot enabled [#10760](https://github.com/scylladb/scylladb/issues/10760) - Stability: Accidentally quadratic behavior when a large number of range tombstones is present in a partition has been [fixed](https://github.com/scylladb/scylladb/commit/7f80602b010a973dd24953cf39161699e7afcb42). [#11211](https://github.com/scylladb/scylladb/issues/11211) - Stability: sstables crawling reader can emit duplicated partition end. This issue affects scylla’s scrub compaction (in all modes) as well as the validate operation of the scylla-sstable tool. [#11421](https://github.com/scylladb/scylla/issues/11421) - Stability: 2 Nodes failed after bloom\_filter\_fp\_chance was modified to an unreasonable low number [#11524](https://github.com/scylladb/scylladb/issues/11524) - Stability: Service Levels: Node crashes during parsing of service level creation with unreserved keywords [#11774](https://github.com/scylladb/scylladb/issues/11774) - UX: Failure to apply a failed batchlog is silent [#10636](https://github.com/scylladb/scylladb/pull/10636) ---
**Author:** ![Tomersan](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tomersan/32/41_2.png) [@Tomersan](https://forum.scylladb.com/u/Tomersan)\ **Post date:** [January 9, 2023, 9:00pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-1-4/241/2 "2023-01-09T21:00:09Z")
Let’s make sure the main release notes [page](https://www.scylladb.com/product/release-notes/) has the link to this (and every) release. Thanks!