# \[RELEASE\] ScyllaDB Enterprise 2024.2.1 **URL:** https://forum.scylladb.com/t/release-scylladb-enterprise-2024-2-1/4101 **Category:** Release Notes **Tags:** enterprise, enterprise-release, enterprise-2024-2 **Created:** [December 8, 2024, 1:49pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-2-1/4101 "2024-12-08T13:49:17Z") **Posts on this page:** 1 **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: [December 8, 2024, 1:49pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-2-1/4101/1 "2024-12-08T13:49:17Z")
The ScyllaDB team announces ScyllaDB Enterprise 2024.2.1, a bug-fix production-ready ScyllaDB Enterprise patch release for [ScyllaDB Enterprise 2024.2 Feature (Short Term Support) Release.](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-2-0/3210) 2024.2.1 patch release includes multiple minor bug fixes. Related Links - [Get ScyllaDB Enterprise 2024.2](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-2-0/3210) (customers only, or 30-day evaluation) - [Upgrade Guide - ScyllaDB Enterprise 2024.1 to 2024.2](https://enterprise.docs.scylladb.com/branch-2024.2/upgrade/upgrade-enterprise/upgrade-guide-from-2024.1-to-2024.2/upgrade-guide-from-2024.1-to-2024.2-generic.html) - [Upgrade - ScyllaDB 6.0 to ScyllaDB Enterprise 2024.2](https://enterprise.docs.scylladb.com/branch-2024.2/upgrade/upgrade-enterprise/upgrade-guide-from-2024.1-to-2024.2/upgrade-guide-from-2024.1-to-2024.2-generic.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): CQL and correctness related - A rare case when data in memtable is not considered when deciding whether expired tombstone can be discarded during read. [#20916](https://github.com/scylladb/scylladb/issues/20916) Alternator - Amazon DynamoDB-compatible API - The Alternator /localnodes REST API returns nodes local to the current datacenter. It is now enhanced to be able to return other datacenters, and to restrict the returned nodes to a specific rack. This can help reduce networking costs and latency in the [Alternator Load Balancer](https://github.com/scylladb/alternator-load-balancing) and already implemented in the [Java version](https://github.com/scylladb/alternator-load-balancing/pull/40) [#12147](https://github.com/scylladb/scylladb/issues/12147) - The Alternator /localnodes endpoint will not return nodes that are temporarily down. [#21538](https://github.com/scylladb/scylladb/issues/21538) Tablets - Failed to complete splitting of table due to raft::request\_aborted (Request is aborted by a caller)] while scylla stopped during Rollback rolling-upgrade [#20890](https://github.com/scylladb/scylladb/issues/20890) - When a tablet is split into two, tombstone garbage collection becomes more complicated, since sstables for the tablet exist in both pre-split and post-split state, causing possible data resurrection during tablet split preparation [#20044](https://github.com/scylladb/scylladb/issues/20044) - Prevent tablet metadata with too many pending replicas from being saved to disk [#20043](https://github.com/scylladb/scylladb/issues/20043) - After a tablet is migrated away from a node, a cleanup process takes place to remove the tablet’s footprint from the replica. During this process a race can happen the tablet’s compaction strategy is changed concurrently. The result is schema ALTER (add column) in the middle of ongoing tablet migration causes internal error: “Compaction state for table … not found” [#20699](https://github.com/scylladb/scylladb/issues/20699) - A race between tablet split and repair could cause an sstable not to be split among two new tablets, which in turn could prevent the sstable from being loaded on restart. [#20626](https://github.com/scylladb/scylladb/issues/20626) - remove\_node\_during\_local\_index\_build failed. [#18862](https://github.com/scylladb/scylladb/issues/18862) Stability - Hinted handoff: Possible dereferencing a null pointer [#21699](https://github.com/scylladb/scylladb/issues/21699) - a potential use after free, make\_streaming\_consumer passes reference to token\_metadata to check\_needs\_view\_update\_path without holding ptr [#20979](https://github.com/scylladb/scylladb/issues/20979) - raft topology: use-after-free raft\_topology\_cmd\_handler, dereferencing pointer to old topology state after reload [#21220](https://github.com/scylladb/scylladb/issues/21220) Performance - Materialized View building (initiated by [CREATE MATERIALIZED VIEW](https://opensource.docs.scylladb.com/stable/cql/mv.html#create-materialized-view) or [CREATE INDEX](https://opensource.docs.scylladb.com/stable/cql/secondary-indexes.html#create-index)) is now performance-isolated from normal reads and writes. [#21232](https://github.com/scylladb/scylladb/issues/21232) - Repair performance in mixed-shard configurations (where different nodes have different shard counts) has been substantially improved. [#21113](https://github.com/scylladb/scylladb/issues/21113) - node-exporter: Disabled the hwmon temperature collector, as it causes bad performance on Azure. [#21163](https://github.com/scylladb/scylladb/issues/21163)