# Last week in scylladb.git master (issue #329; 2026-08-09)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-329-2026-08-09/5456>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [August 9, 2026, 4:59pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-329-2026-08-09/5456 "2026-08-09T16:59:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![avikivity](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/avikivity/32/38_2.png) [@avikivity](https://forum.scylladb.com/u/avikivity)\
**Post date:** [August 9, 2026, 4:59pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-329-2026-08-09/5456/1 "2026-08-09T16:59:52Z")

</div>

This short report brings to light some interesting commits to [scylladb.git master](https://github.com/scylladb/scylladb/) from the last week. Commits in the 4307126ef6b..f9b74e63c2e range are covered.

There were 145 non-merge commits from 28 authors in that period. Some notable commits:

  

The multi-version concurrency control (MVCC) implementation [reduced](https://github.com/scylladb/scylladb/commit/cf39bcad695834424805e61682eba8a8338d4a19) its memory usage, allowing more partitions to fit into memtable and cache.

Incremental compaction strategy writes tombstone-only sstables to guard against data resurrection in case of a crash. In some cases the last such sstable could be leaked. It is now [deleted correctly](https://github.com/scylladb/scylladb/commit/c5a0f7eb4e83e50d423fe754171e66e04d786402).

Encryption parameters are [preserved](https://github.com/scylladb/scylladb/commit/6a5b7cc948f608b034ad95ca24062dbdb8006c5c) when rewriting an sstable component.

The CQL transport now support [concurrent mutual-TLS and password authentication](https://github.com/scylladb/scylladb/commit/793b6374a4035caf18313d8ba2d30758972b8eba).

Compaction now avoids compacting [tiny sstables with large ones](https://github.com/scylladb/scylladb/commit/560b0d428be485b7f2ce4932a23592a8b00a3e3d), as this can cause high write amplification. Tiny sstables are more commonplace with tablets.

Restore now runs in the [backup sub-group](https://github.com/scylladb/scylladb/commit/3e47fa05ee6d1757cce47000aec0369f613a1fd7) of the maintenance scheduling group.

A new [scylla-perf-collector sub-package](https://github.com/scylladb/scylladb/commit/ecd6d64fdc43a1cea8d3957388a1b0835513ef4b/) contains a background performance profile collection service.

Digests of all sstable components are now [validated](https://github.com/scylladb/scylladb/commit/f1cfb3e5def4a02b52f7b687537e4cbab3043c69) during streaming.

The obscure automatic naming of bind variables feature can now name them in [lower-case](https://github.com/scylladb/scylladb/commit/ae279f93ca37950c438fa66f6770aa51b6402332) for compatibility with older versions. Name your bind variables explicitly.

A rare corruption in lz4 decompression was [fixed](https://github.com/scylladb/scylladb/commit/4da0c723570db1bd85343664973e7897c39711f0).

The S3 driver now handles [zero-length objects](https://github.com/scylladb/scylladb/commit/11d2e2522a589d0f44c2666d0f90af66b937ab7b).

When changing the replication factor, the load balancer now better [distributes](https://github.com/scylladb/scylladb/commit/749a97736f7321c37316a77fa80844feeb75dd5e) migrations across shards.

Raft now [decouples](https://github.com/scylladb/scylladb/commit/e84e1dc09f5698f3a10a77fb57748f4d2bcf0771) commits from commit applications.

Alternator, ScyllaDB’s implementation of the DynamoDB API, now supports [pre-filtering](https://github.com/scylladb/scylladb/commit/9b3b99e1d776814ecf655232023aec1d66673ad0) of vector searches.

There is now a [dedicated permission](https://github.com/scylladb/scylladb/commit/6c05ec92a5a62ef215398413e18c410abe6fcda1) for the full-text-search index service.

A livelock when a rack has no available nodes was [fixed](https://github.com/scylladb/scylladb/commit/ddf0dd60796022fd1767bbe018cd2142cd66bd0f).

Alternator, ScyllaDB’s implementation of the DynamoDB API, now preserves [goodput](https://github.com/scylladb/scylladb/commit/554ae522ce7fa0d501382006b39039d9758cc2df) better on overload.

There is now a [metric](https://github.com/scylladb/scylladb/commit/b972ce2240716867c363a9fd868a011cee5c6f11) for read-repairs that actually repaired something.

backup now [tolerates](https://github.com/scylladb/scylladb/commit/3f489173c1483f5fd72f3719c27b0b41f3e0c89b) a racing DROP TABLE.

The TRUNCATE statement USING TIMEOUT clause can now use [bind variables](https://github.com/scylladb/scylladb/commit/ae5083c68f0d24c688ff106bccc27ed87fa197ae).

  

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