The ScyllaDB team is pleased to announce the release of ScyllaDB 2026.2.11, a production-ready patch release for ScyllaDB 2026.2 Short Term Support (STS) Minor Feature Release.
More information on ScyllaDB Version Support Policy is available here.
Related Links
Bug Fixes
The following issues are fixed in this release.
Compaction
-
If an incremental compaction was interrupted at its final step (for example, by a concurrent tablet split or migration), an unused temporary SSTable could remain on disk until the next restart. Such SSTables are now removed even if the compaction does not complete, so disk space is reclaimed promptly.
scylladb#32196 -
Setting a Leveled Compaction Strategy
sstable_size_in_mbabove the 32-bit range inCREATE TABLEorALTER TABLEpassed validation but could later crash the node during schema commit. Such out-of-range values are now rejected up front.
scylladb#31785
Configuration
- The recommended I/O throttling configuration is updated. It is now recommended to limit all background I/O (streaming, maintenance compaction, and backup) with
maintenance_io_throughput_mb_per_sec, set to 75% of the network bandwidth, and to leavestream_io_throughput_mb_per_secandbackup_io_throughput_mb_per_secunthrottled. Existing configurations keep working as before: ifmaintenance_io_throughput_mb_per_secis not set, the value ofstream_io_throughput_mb_per_secapplies to all background I/O.
scylladb#32518
CQL
-
A query that used a bind variable inside an aggregate’s argument (for example,
max(intasblob(?))) or applied to its result (for example,max(m)[?]) could cause the node to restart. Aggregates are now evaluated with the query options, so such queries return the expected results, with or withoutGROUP BY.
scylladb#32841 -
A query that combined a global secondary index on a static column with a clustering-key restriction could cause the node to restart. The clustering-key restriction is no longer pushed into the index lookup, and it is still enforced when reading the base table, so such queries now return correct results.
scylladb#12829, scylladb#32748 -
A
CREATE MATERIALIZED VIEW,ALTER MATERIALIZED VIEW, orCREATE INDEXstatement that set an invalid compaction sub-option was not checked when the statement was prepared, so it could crash the node during schema commit, and afterwards the affected view could not be dropped through CQL. Compaction sub-options for views and indexes are now validated up front, the same as for tables, and options unknown to the chosen compaction strategy are also rejected.
scylladb#31785
Hinted Handoff
- When a hint segment contained an unreadable entry, hints from that segment that had not yet been delivered could be discarded, or the segment could be retried repeatedly. Such a segment is now handled like any other segment: hints that can be read are retried until delivered, and the segment is removed afterward. This improves hint delivery and consistency between replicas.
scylladb#32747
Lightweight Transactions (LWT)
- For tables in tablets keyspaces, writes to the per-table Paxos state tables did not wait for the commitlog to sync in the default
periodiccommitlog mode, so an acknowledged Paxos promise or accept might not be retained after an unclean node stop. Paxos state writes now always wait for the commitlog sync, preserving linearizability of LWT operations on tablets tables.
scylladb#32718
Monitoring
-
During topology operations such as tablet repair,
barrier_and_drainlogged progress at the info level on every shard and for every closed session, which could produce enough log volume to trigger journald rate limiting. Barrier arrival and completion are now logged once per node at the info level, with per-shard and per-session details moved to the debug level, keeping logs concise and complete.
scylladb#32560 -
Tablet repair logged several per-shard and per-request messages at the info level, which could flood the system journal and cause other log messages to be suppressed. These messages are now logged at the debug level, while messages that report an actual hints or batchlog flush stay at the info level, reducing log volume during tablet repair without losing relevant information.
scylladb#32925
Networking
- With RPC compression enabled, an internode message could, in rare cases, be decompressed incorrectly and rejected with an RPC checksum error, because the LZ4 decompression ring buffer was slightly too small. The buffer now includes the margin required by LZ4, so compressed internode messages are always decoded correctly.
scylladb#32536
Performance
- On every topology change, including each tablet migration stage, a sanity check read the entire current CDC generation, which caused reactor stalls on large clusters. The check now reads a single row, removing these stalls during tablet migrations and other topology changes.
scylladb#32901
Reliability
-
When a write timed out on a remote replica, the client received a
WriteFailureerror, whereas the same timeout on the coordinator’s own replica returnedWriteTimeout. Because drivers retryWriteTimeoutbut notWriteFailure, such writes were not retried. Clients now consistently receive a retryableWriteTimeouterror in both cases.
scylladb#32746 -
On a node with a slow disk, enabling the
LARGE_DATA_VIRTUAL_TABLEScluster feature dropped the legacysystem.large_*tables inside a group 0 operation, which could delay group 0 long enough for a joining node’s startup to time out. The legacy tables are now dropped in the background, so group 0 stays available and nodes join as expected.
scylladb#32622
Repair
-
A full incremental repair could temporarily treat already-repaired data as unrepaired. With
tombstone_gc = {'mode': 'repair'}, this could cause a tombstone to be purged too early, so deleted data could reappear. Full incremental repair now leaves already-repaired data unchanged.
scylladb#32197 -
Rebuilding a tablet during node replace,
removenode, or a replication factor change always ran a full repair between the remaining replicas, which could make these operations take a long time on large nodes. The rebuild repair now compares only unrepaired data, since data already marked as repaired by incremental repair is identical on all replicas. This can significantly shorten replace and removenode operations on clusters that use incremental repair. The new behavior is enabled automatically once all nodes in the cluster are upgraded.
scylladb#32519
Stability
-
Dropping a table that has CDC enabled, or a tablets-based table that has used LWT, could trigger nested schema-change notifications that the notifier doesn’t support. If a listener was being unregistered at the same time (for example, during shutdown), the operation could hang. These paths now use the nested-safe notification calls, so
DROP TABLEandALTER TABLEwork reliably in these cases.
scylladb#31939 -
On a heavily loaded node, loading the service level configuration during startup could time out and stop the node from starting. This load no longer times out, so nodes start reliably under load.
scylladb#32707
Tablets
- A memtable write waiting for available memory was not taken into account when a tablet split was acknowledged, so the write could land in the pre-split group and cause the node to restart when the split was finalized. Pending writes are now tracked, and the split is acknowledged only after they complete.
scylladb#32558