Last week in scylladb.git master (issue #310; 2026-02-22)

This short report brings to light some interesting commits to scylladb.git master from the last week. Commits in the 69249671a76..e8efcae9919 range are covered.

There were 129 non-merge commits from 27 authors in that period. Some notable commits:


The permissions caching system was revamped so that every shard has its own cache; instead of cache entries timing out, the cache is fully coherent. This improves performance, decreases the lag between changing permissions and observing the effects, and improves behavior when many clients restart.

Audit to is now enabled by default, with the audit table as destination.

Vector search similarity function performance was improved.

S3 upload concurrency is now limited to 16.

When streaming sstables as part of tablet migration, we now release the storage of each sstable as it is streamed. This reduces storage amplification if sstables are compacted away during streaming.

The frozen toolchain switched the compiler cache from ccache to sccache. Users of the frozen toolchain may wish to update their compiler cache configuration.

Fencing prevents stale requests (due to topology changes) from executing on the wrong node. It was improved so that LWT requests do not generate (harmless) errors during tablet migration.

A bug that caused the connection storm protection code to trigger too soon. This is now fixed.

ScyllaDB with vnodes has two methods for data transfer - repair-based node operations and streaming. It will now default to streaming for scale-in and scale-out operations.

Tablet migration concurrency was reduced to 2 concurrent migrations per shard. This reduces the time it takes to remove storage load from the source node and reduces the risk of running out of space.


See you in the next issue of last week in scylladb.git master!