# Last week in scylladb.git master (issue #332; 2026-09-06)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-332-2026-09-06/5492>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [September 6, 2026, 8:27pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-332-2026-09-06/5492 "2026-09-06T20:27:08Z")\
**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:** [September 6, 2026, 8:27pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-332-2026-09-06/5492/1 "2026-09-06T20:27:08Z")

</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 dc4ad9bfdb9..94c9cb72a83 range are covered.

There were 178 non-merge commits from 38 authors in that period. Some notable commits:

  

Tablet allocation to shards now takes into account that they can be of [wildly differing sizes](https://github.com/scylladb/scylladb/commit/b0c511bf0599959dd236145546c221f47cf807dd) due to vnode-to-tablet migration, at least until their sizes are automatically healed.

A token-range repair that spans [multiple vnodes](https://github.com/scylladb/scylladb/commit/8a1a7e427a24cb6e545c2f50a6185909bd0d4781) is now handled correctly.

Gossip now [coalesces](https://github.com/scylladb/scylladb/commit/95d274f7f405e6fa697c9a2bbc53966529d76305) pending states to avoid memory explosion due to backlog.

There is now a tool to help [estimate gains](https://github.com/scylladb/scylladb/commit/dc17169cf640f2961fcf2daf77c08e1c42235e2d) from compression.

Logstor is a new experimental storage engine aimed at high performance key/value workloads. It now supports the [SELECT FROM MUTATION\_FRAGMENTS()](https://github.com/scylladb/scylladb/commit/afe9591b04ac9ffa3dc055647c8aa00134e3696c) statement.

The query statistics are now correct when a page was [cut in the middle](https://github.com/scylladb/scylladb/commit/f3ba5492339df218ce09fb3ea1c234248e637e34) of a partition.

The compaction manager will now assign a [heavier weight](https://github.com/scylladb/scylladb/commit/d9859de986f40c956246c9e05e0d30d12d8169fa) to tiny sstables, as the cost of compacting them is not proportional to their small size.

A user-requested repair that blocks a topology change operation will now be [aborted](https://github.com/scylladb/scylladb/commit/5f352afcf41aa49a2a9c8062831f92d729200a62) to let the topology operation proceed.

Descriptor attributes of sstables on object storage are now [visible](https://github.com/scylladb/scylladb/commit/3811ab332f8ca45483c55139dc8997ebf5011376).

There is now a new CLI framework for [analyzing](https://github.com/scylladb/scylladb/commit/8ac3afd80fd39b9e6341ef94671c3e134787c7d3) tablet load balancing.

ScyllaDB reclaims memory used by Bloom filters if they consume too much. If two such sstables had the same Bloom filter size, we might have not restore the filter when memory becomes available. This is now [fixed](https://github.com/scylladb/scylladb/commit/2252f33bb2e7c5e13bb1f8d0e480e6be798efe38).

A large allocation during write throttling was [fixed](https://github.com/scylladb/scylladb/commit/a4435bea58c64c5d7415d7435c9e522a619960f6).

A restore could have left a table in a state where it cannot change its tablet count. This is now [fixed](https://github.com/scylladb/scylladb/commit/720c45f6efed90c4f3aa519bbd0c79ba159eefe5).

Alternator, ScyllaDB’s implementation of the DynamoDB API, now fully implements [composite-key global indexes](https://github.com/scylladb/scylladb/commit/2225cf2828c6f34f0fe7135c232c75f2776b69d5) (continuation from previous week’s report).

Size-tiered compaction strategy calculations were [optimized](https://github.com/scylladb/scylladb/commit/6d4200933aaea2030b33191c2165255379ba136d).

The sizes of sstables that had a component rewritten is now [accounted](https://github.com/scylladb/scylladb/commit/f6400f843a3354eaea7919d37189acf235fa8af6) correctly.

Tablet-aware restore is now [multi-datacenter](https://github.com/scylladb/scylladb/commit/c0bc141e0d3fa4c70dafe2da74c478a14155a8b0) capable.

Validation of tables during statement execution is now more [accurate](https://github.com/scylladb/scylladb/commit/3330650feec116bb73ec3b81237170683813bee5) (and slightly faster).

The system.config virtual table now [exposes](https://github.com/scylladb/scylladb/commit/fd87c3cf73c92a50ecd38bdcd5de993bc694a858) whether a value is in use or deprecated.

The schema for a table snapshot now includes [dropped columns](https://github.com/scylladb/scylladb/commit/0f3ec454b39f5e7455fc5276ec23799af5db2e87) for more accurate restore.

Load-and-stream now generates [fewer topology requests](https://github.com/scylladb/scylladb/commit/e13e8d957b8cc7f9afe2096874de80b5f96464a7), interfering less with tablet load-balancing.

Linearization of raft commands not yet committed was [improved](https://github.com/scylladb/scylladb/commit/c91330947ff981a004043e6df8c0c11cdc5d9b1e).

  

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