# Last week in scylladb.git master (issue #334; 2026-09-20)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-334-2026-09-20/5507>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [September 20, 2026, 3:47pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-334-2026-09-20/5507 "2026-09-20T15:47:19Z")\
**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 20, 2026, 3:47pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-334-2026-09-20/5507/1 "2026-09-20T15:47:19Z")

</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 2e8e9f874f8..8066859d359 range are covered.

There were 131 non-merge commits from 24 authors in that period. Some notable commits:

  

The tablet load balancer now [refreshes load statistics](https://github.com/scylladb/scylladb/commit/96c602300f6b0309e0011955ec2620f97c88cf38) if it fails to rearrange them post split/merge, avoiding a load-balancing stall until the next refresh period.

The table size estimation logic, used by vnode-to-tablets migration to select the right tablet count, was [fixed](https://github.com/scylladb/scylladb/commit/5bec7489c8abbb186a33c1d2791cba70fe9d94d6).

The partitioned\_sstable\_set data structure is used to hold sstables for run-oriented compaction strategies, (Incremental Compaction Strategy and Leveled Compaction Strategy). It now uses a [blocked array](https://github.com/scylladb/scylladb/commit/e05d2d0df6a2e46a32e614149255a12714e01020) rather than an interval map, for reduced memory consumption in the worst case.

A commitlog bug involving [lost tracking](https://github.com/scylladb/scylladb/commit/9e1d0504475a25bb49e446c451d8a560e7330319) of a commitlog segment under the conditions of a mutation that spans multiple segments and timeouts was fixed.

A table’s tablet hints now [survive the loss](https://github.com/scylladb/scylladb/commit/92421d4c7f48b36f9b5cab58b9dea5a3cf6ca582) of the node driving restore.

The Google Cloud Storage driver now [correctly interprets](https://github.com/scylladb/scylladb/commit/b1f48c7369c85d36e979bed9854cc32f52e7972d) a 308 Resume Incomplete response with no range header.

The tablet load balancer caps the concurrency of tablet streaming operation per shard. This is now also [enforced](https://github.com/scylladb/scylladb/commit/9d8c6c57e810f7f4aa51797f976bc3a555e5d871) for rebuilds due to replication factor changes.

The DESC modifier for a clustering key [no longer leaks](https://github.com/scylladb/scylladb/commit/cedeefb466a5444ccfa2f5a69fc0e13b417a61f3) into CQL tuple comparisons.

Compaction sub-options are now [validated](https://github.com/scylladb/scylladb/commit/939d6ac9b4b8bbfbb3aae221f82b27f092277784) for materialized views and indexes.

The automatic vnodes-to-tablets migration system was [marked as generally available](https://github.com/scylladb/scylladb/commit/05db2071dfff87280eb8d69529bc631347547e0c).

Indexed SELECT statements now [re-validate](https://github.com/scylladb/scylladb/commit/67cebf1c7868722754570c2977761c92028e8cc7) the index key in the base table rows to avoid inconsistent responses due to replication lag.

The `nodetool stop COMPACTION` command now [stops major compaction](https://github.com/scylladb/scylladb/commit/2125b2297b23df009bd5ac88ea31faad9d30cc16) as well.

  

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