The ScyllaDB team is pleased to announce the release of ScyllaDB 2026.1.11, a production-ready patch release for ScyllaDB 2026.1 Long Term Support (LTS) Release.
More information on ScyllaDB Version Support Policy is available here.
Related Links
Bug Fixes
The following issues are fixed in this release.
Compaction
-
A race between compaction split bypass and regular compaction selection is now resolved. A split bypass compaction racing with a concurrently selected regular compaction could result in incorrect compaction behavior. The fix ensures proper serialization between these two compaction paths.
scylladb#30990 -
A stale-snapshot race between the split replacer and the regular compaction picker is now fixed. Under certain conditions, a split compaction and a
concurrent regular compaction could observe inconsistent snapshots of the SSTable set, leading to undefined behavior. Two related race conditions are addressed in this fix.
scylladb#30990 -
Incremental compaction with garbage collection enabled could leave an SSTable on disk that was never registered or deleted. This occurred when the tail of the compacted stream was entirely purgeable. On clusters with tablets enabled, the leaked SSTable could later prevent the node from restarting until the file was manually removed. Garbage-collected SSTables that are not consumed during compaction are now properly marked for deletion at compaction completion, eliminating the leak and the associated risk of data resurrection or failed restarts.
scylladb#31032
Materialized Views (MV)
- A node abort could occur during shutdown due to an incorrect teardown sequence in the materialized view subsystem, where internal resources could be accessed after being destroyed. The fix ensures proper sequencing of shutdown operations.
scylladb#30933
Storage
-
The S3 client could misclassify errors or lose diagnostic information when an S3-compatible endpoint returned a non-standard error response. This included OCI Object Storage, where transient errors such as rate-limit responses could be incorrectly treated as fatal rather than retried. Some permanent errors were also incorrectly retried. Error classification is now hardened to preserve diagnostic context, stay in sync with the AWS SDK error set, and correctly handle retryable and non-retryable errors.
scylladb#30902 -
A restore operation on tablet-enabled clusters could abort due to a floating-point rounding error in progress tracking. When SSTable batches were
divided across tablets, accumulated rounding imprecision could push the progress counter marginally past its expected total, triggering an assertion. Progress tracking now tolerates this rounding error without aborting.
scylladb#30998