# \[Release\] ScyllaDB 2026.2.9

**URL:** <https://forum.scylladb.com/t/release-scylladb-2026-2-9/5546>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, scylladb-2026-2\
**Created:** [October 16, 2026, 10:36am UTC](https://forum.scylladb.com/t/release-scylladb-2026-2-9/5546 "2026-10-16T10:36:06Z")\
**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:** [October 16, 2026, 10:36am UTC](https://forum.scylladb.com/t/release-scylladb-2026-2-9/5546/1 "2026-10-16T10:36:06Z")

</div>

The ScyllaDB team is pleased to announce the release of **ScyllaDB 2026.2.9** , a production-ready patch release for [ScyllaDB 2026.2 Short Term Support (STS) Minor Feature Release](https://forum.scylladb.com/t/release-scylladb-2026-2/5426 "https://forum.scylladb.com/t/release-scylladb-2026-2/5426").

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

## **Related Links**

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

- [Upgrade ScyllaDB 2026.2 (Patch Upgrade)](https://docs.scylladb.com/manual/branch-2026.2/upgrade/upgrade-guides/upgrade-guide-from-2026.x.y-to-2026.x.z.html "https://docs.scylladb.com/manual/branch-2026.2/upgrade/upgrade-guides/upgrade-guide-from-2026.x.y-to-2026.x.z.html")

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

## **Bug Fixes**

The following issues are fixed in this release.

### **Compaction**

- `nodetool stop COMPACTION` no longer stopped major compactions, so you could only stop a running major compaction through the REST API. `nodetool stop COMPACTION` now stops both regular (automatic) and major compactions again. A new `REGULAR` type stops only regular compactions (`nodetool stop REGULAR`), and `MAJOR` stops only major compactions. nodetool and the REST API now share the same compaction-type validation, so nodetool rejects an invalid type right away with a clear error message.  
[scylladb#31974](https://github.com/scylladb/scylladb/pull/31974 "https://github.com/scylladb/scylladb/pull/31974")

- If a node shut down early during startup, before compaction was enabled, the compaction manager’s shutdown path could leave a configuration-update action running. Shutdown now drains that action, so a node stops cleanly after an early startup error.  
[scylladb#31976](https://github.com/scylladb/scylladb/pull/31976 "https://github.com/scylladb/scylladb/pull/31976")

### **CQL**

- When a secondary index was temporarily out of sync with its base table, for example because of replication lag, a query that used the index could return rows that did not match the `WHERE` clause. ScyllaDB now checks every row read through an index against the base row before returning it, so indexed queries always return results that match their predicates. With this change, indexed queries with a single predicate use the same filtering path as indexed queries that already had more than one predicate.  
[scylladb#31746](https://github.com/scylladb/scylladb/pull/31746 "https://github.com/scylladb/scylladb/pull/31746")

- `SELECT ... FROM MUTATION_FRAGMENTS(<table>)` ignored `GROUP BY` and returned one row aggregated over all fragments instead of one row per group. Aggregates over more than one internal page also came back as several partial rows. For example, a `COUNT` over 25,000 fragments returned 10000, 10000, and 5000. Aggregate and `GROUP BY` queries on `MUTATION_FRAGMENTS()` now page and group correctly and return the expected results.  
[scylladb#31972](https://github.com/scylladb/scylladb/pull/31972 "https://github.com/scylladb/scylladb/pull/31972")

### **Stability**

- Some internal queries in system tables, such as lookups in `system.repair_tasks` and `system.topology_requests`, put parameter values directly into the query text. Each distinct value was cached as a separate prepared statement that was never evicted, so memory use grew steadily over time on long-running nodes. These queries now use bound parameters, which keeps the internal statement cache bounded.  
[scylladb#31975](https://github.com/scylladb/scylladb/pull/31975 "https://github.com/scylladb/scylladb/pull/31975")

### **Storage**

- A backup task still waiting for the snapshot lock ignored abort requests. It kept running, then started uploading after the Scylla Manager run that created it had stopped. Over time this could build up a large queue of leftover backup tasks on a node. Queued backup tasks now respond to abort, so stopping a backup run also cancels its pending tasks.  
[scylladb#31871](https://github.com/scylladb/scylladb/pull/31871 "https://github.com/scylladb/scylladb/pull/31871")

- The S3 chunked download path retried errors immediately without pacing, and retried non-retryable errors indefinitely, which could leave a read waiting forever. It also didn’t report refusals to the request throttling controller. Downloads now use the standard retry strategy with backoff and a bounded number of retries, and report to the throttling controller. Reads from object storage now behave predictably when the endpoint is under pressure.  
[scylladb#31973](https://github.com/scylladb/scylladb/pull/31973 "https://github.com/scylladb/scylladb/pull/31973")

- During sstable directory processing, such as a `nodetool refresh` that needs to change SStable levels, one shard could claim an SStable another shard was still creating and schedule its components for removal. Each shard now handles only SStables that are fully created, so refresh completes reliably and keeps all SStables.  
[scylladb#31971](https://github.com/scylladb/scylladb/pull/31971 "https://github.com/scylladb/scylladb/pull/31971")

### **Tablets**

- After a tablet split or merge, tablet migration could stall for up to 60 seconds (until the next periodic load-stats refresh) if a replica had not yet reported its size, for example a node that had just joined. A load-stats refresh is now triggered immediately in this case, so migration no longer waits.  
[scylladb#31693](https://github.com/scylladb/scylladb/pull/31693 "https://github.com/scylladb/scylladb/pull/31693")

- A `DROP KEYSPACE` or `DROP TABLE` that ran while tablet migration was streaming SStables into the same table could lead to a node restart. Streaming now holds the table for the duration of the operation, so the drop waits for in-flight streaming to finish.  
[scylladb#31855](https://github.com/scylladb/scylladb/pull/31855 "https://github.com/scylladb/scylladb/pull/31855")

- The streaming concurrency cap for replication-factor-change rebuilds, introduced in 2026.2.8, has been reverted because it could delay rebuilds indefinitely in some topologies. RF-change rebuilds behave as they did before 2026.2.8.  
[scylladb#31929](https://github.com/scylladb/scylladb/pull/31929 "https://github.com/scylladb/scylladb/pull/31929")
