[Release] ScyllaDB 2026.2.10

Release Notes
, ,
1

The ScyllaDB team is pleased to announce the release of ScyllaDB 2026.2.10, 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.

Alternator

  • DescribeTable did not return WarmThroughput for a table or ProvisionedThroughput for its Global Secondary Indexes (GSIs), so tools that expect these fields, such as the Terraform AWS Provider, could not manage Alternator tables. DescribeTable now returns WarmThroughput for the table and for each active GSI, and returns each GSI’s own ProvisionedThroughput. CreateTable and UpdateTable now validate GSI ProvisionedThroughput the same way DynamoDB does: it is required for PROVISIONED tables, rejected for PAY_PER_REQUEST tables, and both capacities must be at least 1. In addition, CreateTable now returns the complete TableDescription, and a table ProvisionedThroughput of zero or less is rejected. As a result, Alternator works better as a drop-in DynamoDB replacement with standard infrastructure-as-code tools.
    scylladb#32469

Audit

  • Audit writes used timeouts of up to one hour. If a replica did not respond to an audit write (for example, during a rolling upgrade), topology operations could stall for that long, and a joining node could remain in the bootstrap state. Audit writes now use the same five-second timeouts as tracing writes, so topology operations continue promptly.
    scylladb#32362

Compaction

  • With Leveled Compaction Strategy (LCS), a table with a small amount of data waiting to be compacted could be reported as having no pending compactions. This pending work is now counted, so nodetool compactionstats and tools that rely on it correctly report outstanding compaction work. Compaction behavior itself is unchanged.
    scylladb#32094

  • When a row had a shadowable tombstone and a regular tombstone with timestamps in different time windows, the timestamp-based splitting writer wrote both into the same time window. This could cause Time Window Compaction Strategy (TWCS) reshape to repeat endlessly. Each tombstone part is now written to the time window that matches its own timestamp, so reshape finishes as expected.
    scylladb#31999

  • If a node shut down early during startup, before compaction was enabled, a late disk-space-monitor callback could re-enable the compaction manager while it was stopping. Shutdown now moves the compaction manager into its stopped state, so a node stops cleanly after an early startup error.
    scylladb#32031

  • When a keyspace was dropped shortly before a node was stopped, an error during shutdown could interrupt the schema change and, in some cases, cause the node to restart. Nodes now shut down cleanly in this scenario.
    scylladb#32284

Materialized Views (MV)

  • The view building worker kept references to the staging sstables registered with it. When incremental repair or a tablet merge rewrote one of those sstables, the worker kept retrying view updates from the outdated sstable and never completed them. The worker now looks up staging sstables in the table’s current sstable set when it processes them, so view building continues correctly alongside incremental repair and tablet merges.
    scylladb#32102

Performance

  • When many pending writes were cancelled at once, the node could use an unusually large amount of memory and experience latency spikes. Cancellations are now processed in smaller batches, which reduces latency spikes.
    scylladb#32170

Reliability

  • When commitlog replay encountered damaged segments, the cache for large (fragmented) commitlog entries could mix fragments from different shards, because fragment IDs are only unique per shard. The cache is now kept per shard, so large entries are replayed correctly.
    scylladb#32069

Repair

  • Before a repair, a node replays pending hints and batchlog entries. Batchlog replay had no time limit, so if it stalled, every later repair on that node was blocked until the node was restarted. Batchlog replay now has a timeout, like hints replay, so later repairs can proceed.
    scylladb#32361

  • Aborting a removenode operation didn’t reach its streaming phase, so the streaming kept running after the abort. An abort requested before streaming began was also lost. Both are now forwarded to the removenode streaming, so the operation stops promptly when you abort it.
    scylladb#32056

Stability

  • Under rare timing conditions, the commitlog could process its segments out of order. Segment ordering is now preserved, which improves commitlog stability.
    scylladb#32193

  • An error while processing a gossip update (for example, under memory pressure) could leave a node with incomplete information about another node, which gossip did not correct afterwards. Incomplete updates are now discarded and the full state is received again, so gossip state stays consistent across the cluster.
    scylladb#32194, scylladb#32198

  • On hosts with an uneven NUMA node layout, a node started with a reduced number of shards (--smp) could fail at startup. Such nodes now start normally.
    scylladb#32460

Storage

  • If an error occurred during an S3 multipart upload, some of the upload’s resources were not released. These resources are now released when an error occurs.
    scylladb#32343

Tablets

  • During a vnodes-to-tablets migration, upgraded nodes could send tablet routing information to drivers before the migration was finalized. If the migration was then rolled back, drivers could continue routing requests based on tablets that no longer existed. Tablet routing information is now sent only after the migration is finalized. Until then, drivers route requests as they did before the migration, and a rollback requires no changes on the client side.
    scylladb#32158

  • When the tablet load balancer planned a group of migrations, it checked the per-shard streaming limits using the number of migrations rather than their combined streaming weight. Rebuild migrations carry a higher weight, so source and target shards could go over tablet_streaming_read_concurrency_per_shard. The check now uses the combined weight, so streaming stays within the configured limits.
    scylladb#32055