# \[Release\] ScyllaDB 2025.4.9

**URL:** <https://forum.scylladb.com/t/release-scylladb-2025-4-9/5381>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, scylladb-2025-4\
**Created:** [May 25, 2026, 8:37am UTC](https://forum.scylladb.com/t/release-scylladb-2025-4-9/5381 "2026-05-25T08:37:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anna](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/anna/32/48_2.png) [@Anna](https://forum.scylladb.com/u/Anna)\
**Post date:** [May 25, 2026, 8:37am UTC](https://forum.scylladb.com/t/release-scylladb-2025-4-9/5381/1 "2026-05-25T08:37:16Z")

</div>

The ScyllaDB team is pleased to announce the release of ScyllaDB 2025.4.9, a production-ready patch release for [ScyllaDB 2025.4 Feature Release](https://forum.scylladb.com/t/release-scylladb-2025-4-0/5222).

Note there is a new Long Term Support (LTS) release [2026.1](https://forum.scylladb.com/t/release-scylladb-2026-1/5327). You are welcome to upgrade to it for the latest and greatest features.

More information on ScyllaDB Version Support Policy is available [here](https://docs.scylladb.com/stable/versioning/version-support-enterprise.html).

## Related Links

- [Get ScyllaDB 2025.4](https://docs.scylladb.com/manual/branch-2025.4/getting-started/install-scylla/index.html)

- [Upgrade ScyllaDB 2025.4 (Patch Upgrade)](https://docs.scylladb.com/manual/branch-2025.4/upgrade/upgrade-guides/upgrade-guide-from-2025.4.x-to-2025.4.y.html#upgrade-scylla-name-src-version-to-new-version-patch-upgrades)

- [Upgrade from ScyllaDB 2025.x to ScyllaDB 2025.4](https://docs.scylladb.com/manual/branch-2025.4/upgrade/upgrade-guides/upgrade-guide-from-2025.x-to-2025.4/index.html)

- [Contact our Support Team](https://www.scylladb.com/customer-portal/#support)

## Bug Fixes

### Administration

- Local system table creation could experience synchronization issues during concurrent operations. The synchronization handling was improved for internal table creation, improving stability during these operations.  
[scylladb#29861](https://github.com/scylladb/scylladb/pull/29861)

### Monitoring

- Diagnostic logging for internal Barrier and drain operations provided limited detail for troubleshooting. Additional logging was added for barrier and drain operations, improving visibility into node state during internal maintenance activities.  
[scylladb#29801](https://github.com/scylladb/scylladb/pull/29801)

- The `system.size_estimates` table could produce incomplete aggregation of SSTable size reports across all shards on a node, resulting in incomplete table size estimates. This is resolved by ensuring metrics from every shard are accurately aggregated, providing cluster administrators with complete and reliable per-node table size estimates.  
[scylladb#29799](https://github.com/scylladb/scylladb/pull/29799)

### Performance

- A potentially long-running operation in the `trie_writer::complete_until_depth()` function could occasionally block shard progress during background tasks. A preemption point was introduced into this function, allowing the shard to yield during long background activities like compaction. This improves latency and overall node responsiveness. [scylladb#29837](https://github.com/scylladb/scylladb/pull/29837)

### Reliability

- An issue could affect a node on shard 0 when concurrent incremental repair operations were running during a scale-out procedure. This is resolved by synchronizing the incremental repair logic with the tablet split mechanism, ensuring stable cluster operations during concurrent scaling and repair activities.  
[scylladb#26041](https://github.com/scylladb/scylladb/issues/26041), [scylladb#27844](https://github.com/scylladb/scylladb/pull/27844)

- SSTable attachment during the streaming process could be incomplete in the consumer, sometimes leaving sealed SSTable files consuming disk space. The fix ensures that these sealed files are properly cleaned up when this occurs, preventing unnecessary disk usage and improving storage management during streaming operations.  
[scylladb#27414](https://github.com/scylladb/scylladb/issues/27414)

- Prepared statement invalidation could lead to stability issues in the CQL layer, potentially affecting CQL service stability. This is resolved by improving internal resource handling during prepared statement invalidation. This change eliminates a source of instability and enhances the reliability of the CQL interface. [scylladb#29812](https://github.com/scylladb/scylladb/pull/29812)