# \[RELEASE\] ScyllaDB Enterprise 2021.1.17

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2021-1-17/214>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2021-1\
**Created:** [January 1, 2023, 8:12am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2021-1-17/214 "2023-01-01T08:12:07Z")\
**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:** [January 1, 2023, 8:12am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2021-1-17/214/1 "2023-01-01T08:12:07Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2021.1.17, 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/).

Note that ScyllaDB Enterprise [2022.1 LTS](https://www.scylladb.com/product/release-notes/scylladb-enterprise-release-2022-1-0/) is the latest stable branch and you are encouraged to upgrade in coordination with the ScyllaDB support team.

Related Links

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

- Stability: Time window compaction strategy (TWCS) major compactions will now [serialize behind other compactions](https://github.com/scylladb/scylla/commit/55bb70a878ae678db555b9d823017bc337f27650), in order to to include all sstables in the compaction input set. [#9553](https://github.com/scylladb/scylla/issues/9553)
- Stability: Mismatched types for base and view columns (leftovers from [#8666](https://github.com/scylladb/scylla/issues/8666) fix)
- Stability: compaction: Make compaction\_manager stop more robust [#11711](https://github.com/scylladb/scylladb/pull/11711)
- Stability: materialized view doesn’t work if there is a “to” column [#9450](https://github.com/scylladb/scylladb/issues/9450)
- 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)
- In Time Window Compaction Strategy compactions, fully expired sstables will be [compacted separately](https://github.com/scylladb/scylla/commit/79b0654d60f51700d7add575f394ea99c44f1fe6), since that can be done by just dropping them. [#9533](https://github.com/scylladb/scylla/issues/9533)
- 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: use-after-free in db/view row\_locker [#12168](https://github.com/scylladb/scylladb/issues/12168)
- Stability: replace nodes are (at times) left in system.peers table - they need to be removed [#8729](https://github.com/scylladb/scylladb/issues/8729)
- 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 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: UndefinedBehavior 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)