# \[RELEASE\] ScyllaDB 2025.1.7 **URL:** \ **Category:** Release Notes\ **Tags:** enterprise, enterprise-release, scylladb-2025-1\ **Created:** [September 14, 2025, 2:53pm UTC](https://forum.scylladb.com/t/release-scylladb-2025-1-7/5096 "2025-09-14T14:53:09Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Aharon\_Blitzer](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/aharon_blitzer/32/1811_2.png) [@Aharon\_Blitzer](https://forum.scylladb.com/u/Aharon_Blitzer)\ **Post date:** [September 14, 2025, 2:53pm UTC](https://forum.scylladb.com/t/release-scylladb-2025-1-7/5096/1 "2025-09-14T14:53:09Z")
The ScyllaDB team announces **ScyllaDB 2025.1.7** , a bug-fix production-ready patch release for [ScyllaDB 2025.1 LTS Release.](https://forum.scylladb.com/t/release-scylladb-2025-1/4692/3) Note there is a new Short Term Support (STS) Feature release [2025.3](https://forum.scylladb.com/t/release-scylladb-2025-3-0/5085). You are welcome to upgrade to it for the latest and greatest features, or stay on the 2025.1 track for long term support. Related Links - [Get ScyllaDB 2025.1](https://forum.scylladb.com/t/release-scylladb-2025-1/4692/3) - [Upgrade from ScyllaDB Enterprise 2024.x to ScyllaDB 2025.1](https://docs.scylladb.com/manual/branch-2025.1/upgrade/upgrade-guides/upgrade-guide-from-2024.x-to-2025.1/index.html) - [Upgrade from ScyllaDB Open Source 6.2 to ScyllaDB Enterprise 2025.1.x](https://docs.scylladb.com/manual/branch-2025.1/upgrade/upgrade-guides/upgrade-guide-from-6.2-to-2025.1/index.html) - [Submit a ticket](https://supportscylladb.zendesk.com/hc/en-us/requests/new) The following issues are fixed in this release: Stability - service/qos: Modularize service level controller to avoid invalid access to a stopped auth::service [#24792](https://github.com/scylladb/scylladb/issues/24792) - Commitlog: segment\_manager::discard\_unused\_segments - separate the modification of the vector (\_segments) from actual releasing of objects [#25709](https://github.com/scylladb/scylladb/issues/25709) - Drop table during tablet cleanup initiated by a tablet migration may crash [#25706](https://github.com/scylladb/scylladb/issues/25706) - gossiper - race condition in gossip::apply\_state\_locally when receiving messages containing removed endpoints that no longer have a valid host id [#25702](https://github.com/scylladb/scylladb/issues/25702), [#25621](https://github.com/scylladb/scylladb/issues/25621) - gossiper can reply with an empty self host id in `gossip_get_endpoint_states_response` during startup [#25831](https://github.com/scylladb/scylladb/issues/25831) - Tablets Repair: A node may crash If a node has many shards and many tablets on each shard [#23632](https://github.com/scylladb/scylladb/issues/23632) - Segmentation fault in scheduling group streaming during tablets streaming after node was decommissioned [#23162](https://github.com/scylladb/scylladb/issues/23162) Optimization - Improved handling of in-progress requests during node shutdown, ensuring requests are allowed to complete successfully. [#24481](https://github.com/scylladb/scylladb/issues/24481) - Removed a large allocation when loading SSTables [#3335](https://github.com/scylladb/scylladb/issues/3335) - raft\_sys\_table\_storage: avoid an extra copy when deserializing log\_entry [#23903](https://github.com/scylladb/scylladb/issues/23903), - seastar\_memory - Removed an oversized allocation changing token\_range\_vectorto use chunked\_vector [#24156](https://github.com/scylladb/scylladb/issues/24156), [#24115](https://github.com/scylladb/scylladb/issues/24115) - storage\_service::maybe\_reconnect\_to\_preferred\_ip() calls the gossiper::get\_host\_id() unnecessarily and can be passed directly as a parameter [#25715](https://github.com/scylladb/scylladb/issues/25715) - Optimized container footprint – The container image size has been minimized to improve efficiency [#25479](https://github.com/scylladb/scylladb/issues/25479) Tracing and logging - Backport ‘reactor: Update seastar submodule to get more info and robustness on segfault’ [scylladb#25681](https://github.com/scylladb/scylladb/issues/25681) - db/hints: Improve logs [#25466](https://github.com/scylladb/scylladb/issues/25466) - Debug logs: deletion\_time formatter prints wrong results [#25556](https://github.com/scylladb/scylladb/issues/25556) - db/commitlog: Extend error messages for corrupted data [#25459](https://github.com/scylladb/scylladb/pull/25459) API and tooling - Warn users about using RF!=Racks with Tablets Keyspaces [#23330](https://github.com/scylladb/scylladb/issues/23330) - storage\_service/get\_natural\_endpoints has no way to pass a key containing a colon character [#24829](https://github.com/scylladb/scylladb/pull/24829) Performance - Alternator, ScyllaDB’s implementation of the DynamoDB API, is now more careful to avoid large contiguous allocations during query/scan operations, as these can cause stalls. [#23535](https://github.com/scylladb/scylladb/issues/23535) - Improve performance of worst case scenario in auth::passwords::detail::hash\_with\_salt [#24524](https://github.com/scylladb/scylladb/issues/24524) - Improve performance for partial repair with a node down and with many tablets [#22413](https://github.com/scylladb/scylladb/issues/22413) - storage\_service: on\_change: frequent system.peers reloads with many peers may cause high CPU usage [#25660](https://github.com/scylladb/scylladb/issues/25660) - system\_keyspace::drop\_truncation\_rp\_records can cause unbound parallelism [#25682](https://github.com/scylladb/scylladb/issues/25682)