# \[RELEASE\] ScyllaDB Enterprise 2024.1.5 **URL:** \ **Category:** Release Notes\ **Tags:** enterprise, enterprise-release, enterprise-2024-1\ **Created:** [June 16, 2024, 8:41am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-1-5/2172 "2024-06-16T08:41:02Z")\ **Posts on this page:** 3\ **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:** [June 16, 2024, 8:41am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-1-5/2172/1 "2024-06-16T08:41:02Z")
The ScyllaDB team announces ScyllaDB Enterprise 2024.1.5, a bug-fix production-ready ScyllaDB Enterprise patch release for [ScyllaDB Enterprise 2024.1 LTS Release.](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-1-0/1292) Improvements in this release: - Alternator Performance improvements. Varies optimization improved the throughput of the Alternator by up to 35%, depending on the workload. - This release adds Workload Prioritization to Alternator, ScyllaDB’s Amazon DynamoDB-compatible API. To use Workload Prioritization, one needs to enable alternator\_enforce\_authorization in the configuration. Read more about this feature[here](https://enterprise.docs.scylladb.com/branch-2024.1/alternator/compatibility#workload-isolation) - Repair: Introduce small table optimization [#15974](https://github.com/scylladb/scylladb/pull/15974) [#16011](https://github.com/scylladb/scylladb/issues/16011) Related Links - [Get ScyllaDB Enterprise 2024.1](https://www.scylladb.com/download/#enterprise) (customers only, or 30-day evaluation) - [Upgrade from ScyllaDB Enterprise 2023.1.x to 2024.1.y](https://enterprise.docs.scylladb.com/branch-2024.1/upgrade/upgrade-enterprise/upgrade-guide-from-2023.1-to-2024.1/upgrade-guide-from-2023.1-to-2024.1-generic.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.4 to ScyllaDB Enterprise 2024.1.x](https://opensource.docs.scylladb.com/stable/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.4-to-2024.1/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): Alternator - Alternator: converting large items to text representation will stall [#18806](https://github.com/scylladb/scylladb/issues/18806) Tracing - Security: A new log message prints out the [Audit](https://enterprise.docs.scylladb.com/stable/operating-scylla/security/auditing.html) status for the cluster. - Tracing: the ability of figuring which shard owns a partition from system.large\_partition by analyzing a corresponding sstable id was broken when moving to UUID based SSTable numbering [#18381](https://github.com/scylladb/scylladb/issues/18381) Instead, one can use [scylla sstable shard-of](https://opensource.docs.scylladb.com/master/operating-scylla/admin-tools/scylla-sstable.html#shard-of) to extract shards which own the specified SSTables. [#16343](https://github.com/scylladb/scylladb/issues/16343) [#18440](https://github.com/scylladb/scylladb/pull/18440) Monitoring - Monitoring: Scylla 2024.1 enables per-table metrics by default on a per-instance level. Some of the metrics, like cache\_hit\_rate, latency and live\_disk\_space were not reported, and missing from the Monitoring Table Dashboard. [#18642](https://github.com/scylladb/scylladb/issues/18642) - Alternator: Scylla Alternator histogram to use Summaries. Alternator reports multiple histograms for operation latencies. Instead it should report a histogram per node and a summary per shard. [#12230](https://github.com/scylladb/scylladb/issues/12230). **To show this Alternator metric, use Scylla Monitoring 4.7.2 or later.** Performance - Performance: In tables with many small partitions (or many partition tombstones), sstable index pages can contain many entries. They are now destroyed gently to [avoid stalls](https://github.com/scylladb/scylladb/commit/e120ba3514ef841c0aa0fd2251079351a2e06640). [#17605](https://github.com/scylladb/scylladb/issues/17605) - repair: add control for repair percentage for partition count estimation [#18615](https://github.com/scylladb/scylladb/issues/18615). The new parameter is [repair\_partition\_count\_estimation\_ratio](https://opensource.docs.scylladb.com/stable/reference/configuration-parameters.html#confval-repair_partition_count_estimation_ratio). The default 10% has not changed. Stability - Stability: clustering\_range intersection() can cause an infinite loop [#18688](https://github.com/scylladb/scylladb/issues/18688) - Stability: direct failure detector: make ping timeout configurable and increase the default, from 300 to 600 ms [#16607](https://github.com/scylladb/scylladb/issues/16607). Failure detector is an internal inter-node mechanism. - Stability: fromJson() or INSERT JSON fails to set a map\ [#18477](https://github.com/scylladb/scylladb/issues/18477) - Stability: handle\_paxos\_accept() fails to record a trace message when done with handling [#18725](https://github.com/scylladb/scylladb/issues/18725) - Stability: mutation\_fragment\_stream\_validating\_filter doesn’t respect validation\_level::none [#18662](https://github.com/scylladb/scylladb/issues/18662). The issue might cause false-positive validation errors during repair/streaming, leading to aborting the operation. - Stability: Scylla crash when reading from mutation fragments with token() filtering [#18637](https://github.com/scylladb/scylladb/issues/18637) - Stability: utils::chunked\_vector fill constructor is exception unsafe [#18635](https://github.com/scylladb/scylladb/issues/18635) - Stability: Wrong exception is printed in build step exception handling [#18423](https://github.com/scylladb/scylladb/issues/18423) Bloom Filter - Performance: ScyllaDB estimates a compaction’s partition count in order to correctly size the Bloom filter. It will now improve the estimate for garbage collection SStables. [#18283](https://github.com/scylladb/scylladb/issues/18283) - bloom-filter: default value for components\_memory\_reclaim\_threshold is too strict [#18607](https://github.com/scylladb/scylladb/issues/18607). Updated from 0.1 to 0.2 in the fix. - Stability: ScyllaDB drops Bloom filters when they use up too much space. It will now reload them when space is available again (for example due to compaction). [#18186](https://github.com/scylladb/scylladb/pull/18186) Other fixed issues - Image: while dropping openssh-server from the ScyllaDB image, other system packages used by ScyllaDB scripts were also dropped.[#17787](https://github.com/scylladb/scylladb/issues/17787) - Config: default [task\_ttl\_in\_seconds](https://opensource.docs.scylladb.com/master/reference/configuration-parameters.html#confval-task_ttl_in_seconds) is 0, but scylla.yaml changes the value to 10. [#16714](https://github.com/scylladb/scylladb/issues/16714) - Tools: Update tools/cqlsh submodule to v6.0.17 [#18652](https://github.com/scylladb/scylladb/pull/18652) - CQL: The algorithm for picking an index for a request is not always deterministic [#7969](https://github.com/scylladb/scylladb/issues/7969) ---
**Author:** ![web333](https://avatars.discourse-cdn.com/v4/letter/w/b38774/32.png) [@web333](https://forum.scylladb.com/u/web333)\ **Post date:** [July 21, 2024, 7:34pm UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-1-5/2172/2 "2024-07-21T19:34:08Z")
> [@tzach](#): > > Varies optimization improved the throughput of the Alternator by up to 35%, depending on the workload. Nice! Is this also available in the open-source version? Are there any benchmark writeups? ---
**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:** [July 22, 2024, 12:16am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2024-1-5/2172/3 "2024-07-22T00:16:47Z")
The improvement is limited to Enterprise, similar to the Enterprise only improvement for CQL in 2024.1.0 We will share more information on Benchmark shortly.