# Last week in scylladb.git master (issue #191; 2023-08-05)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-191-2023-08-05/758>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [August 6, 2023, 11:15am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-191-2023-08-05/758 "2023-08-06T11:15:30Z")\
**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 6, 2023, 11:15am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-191-2023-08-05/758/1 "2023-08-06T11:15:30Z")

</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 1c3d22b717…421a5ad55c range are covered.

There were 132 non-merge commits from 15 authors in that period. Some notable commits:

  

Tablets are a new, experimental way of distributing data across nodes and shards. The tablet load balancer is now able to [concurrently migrate](https://github.com/scylladb/scylladb/commit/dac93b209648e0b7503a64b935eebed776358a2c) tablets to new nodes, and is able to make new decisions while tablets are being streamed.

In CQL, a few functions for dealing with counter types were [added](https://github.com/scylladb/scylladb/commit/a637ddd09c3596d6838d3d562f713b7ee5f00a34).

Alternator, ScyllaDB’s implementation of the DynamoDB API, now [limits](https://github.com/scylladb/scylladb/commit/04e5082d524169d09603bfdf065d496e309e5bcb) embedded expression length and nesting.

A source of high latency in multi-partition scans was [eliminated](https://github.com/scylladb/scylladb/commit/f2c1a214e51185917d41bb2a5011eac388628eae).

Change Data Capture exposes multiple streams to reflect the cluster topology. It is now [more careful](https://github.com/scylladb/scylladb/commit/8bb3732d668128aa4954f2ad33f180b23113fc20) to avoid closing and creating new streams unnecessarily.

Fencing is a way to prevent a coordinator from interacting with replicas when it has an outdated view of cluster topology. This now applies to [counter updates](https://github.com/scylladb/scylladb/commit/0239ba45272fa6d0f41fe7a34125ed018f9d9bbc) too.

ScyllaDB verifies ownership and permissions for its own files. It now [avoids](https://github.com/scylladb/scylladb/commit/c3b23fc03d00984f3def1811095e5cbe0ab35849) doing this for snapshots, as they might be concurrently being deleted by an administrator or scylla-manager.

Cluster features are ScyllaDB’s way of making rolling upgrades seamless - a feature isn’t enabled until all nodes support it. We now propagate cluster features [via Raft](https://github.com/scylladb/scylladb/commit/b835acf853d8cf3553b96fe0aa4f5746304cccc5) rather than gossip for improved reliability.

Most ScyllaDB metrics are per-shard, per-node, but not for a specific table. We now export some [per-table metrics](https://github.com/scylladb/scylladb/commit/cb3b808e3f0cdf27b0edded92e805559d74d7a69). These are exported once per node, not per shard.

There is a new option to specify the number of token ranges to [repair in parallel](https://github.com/scylladb/scylladb/commit/946c6487ee507e5ed54bbd5603b3e2a68d9a3b76).

  

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