# Last week in scylladb.git master (issue #223; 2024-03-24)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-223-2024-03-24/1417>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [March 24, 2024, 4:35pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-223-2024-03-24/1417 "2024-03-24T16:35:26Z")\
**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:** [March 24, 2024, 4:35pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-223-2024-03-24/1417/1 "2024-03-24T16:35:26Z")

</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 7df3acd39c…6bdb456fad range are covered.

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

  

The native `nodetool status` command now [handles joining nodes](https://github.com/scylladb/scylladb/commit/a4e8bea679970059974388e9fdebee72ef6610bd) better.

A reactor stall when reading the materializing very large schemas has been [fixed](https://github.com/scylladb/scylladb/commit/680e37c4af53e3c98c09dfc7f8ed3313eb7af882).

During compaction tombstone garbage collection, we now [skip the bloom filter checks](https://github.com/scylladb/scylladb/commit/2c0b1d1fa772cd1a8831ecfddc00c27570ec8990) if the sstable only contains young data.

During compaction tombstone garbage collection, we now consider the memtable [only if it contains the key](https://github.com/scylladb/scylladb/commit/2c9b13d2d16d332cdc888848d9fa9b248af5efe9). This prevents old data in memtable from preventing tombstone garbage collection.

Tracking of memory within materialized view updates was [improved](https://github.com/scylladb/scylladb/commit/efcb718e0aad43d67f84e30475fa75c44a872653).

The replace operation, when running with the same number of nodes as the replication factor (e.g. typically 3), the node replace operation now [works correctly](https://github.com/scylladb/scylladb/commit/72bbe75d5b81ebccf20be46e5bc123fd18a5a7b6).

There is now [documentation](https://github.com/scylladb/scylladb/commit/70cb1dc8febc6b5e3ceeded4bd2e131f0fed77d4) for initiating upgrade into consistent topology management and recovering from a disaster when it is enabled.

A crash when a view was created while a TRUNCATE operation is in progress was [fixed](https://github.com/scylladb/scylladb/commit/8df2ea3f95622a0c4f7f54f85dd794c96e9db0e3).

The `system.token_ring` virtual table is now [tablet-aware](https://github.com/scylladb/scylladb/commit/21a5911e60cc90c45ed5e3ca6b7d7cd81289b9ad).

The native nodetool command now mimics [Java-style command line handling](https://github.com/scylladb/scylladb/commit/fdeb14b468eda72c18977792cfcd0d4b954a521f) for greater compatibility with scripts.

The native nodetool command can now query effective ownership on a [table basis](https://github.com/scylladb/scylladb/commit/28ed20d65e160f86e31da3e046992d018cbc9ffa), useful with tablets.

Raft now handles lost quorums [more flexibly](https://github.com/scylladb/scylladb/commit/4359a1b460d3f4a2f277ae26a3769878e0757a3e), allowing callers to decide whether they want to timeout or not.

The service level subsystem [moved its storage](https://github.com/scylladb/scylladb/commit/f23f8f81bfc5fb373af691bd3d99820dba5ec48e) from the system\_distributed keyspace to a new table system.service\_levels\_v2, managed by raft group 0. Data is automatically migrated.

  

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