# Last week in scylladb.git master (issue #194; 2023-08-27)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-194-2023-08-27/809>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [August 27, 2023, 10:41am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-194-2023-08-27/809 "2023-08-27T10:41:00Z")\
**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 27, 2023, 10:41am UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-194-2023-08-27/809/1 "2023-08-27T10:41:00Z")

</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 7275b8967c…9806bddf75 range are covered.

There were 86 non-merge commits from 17 authors in that period. Some notable commits:

  

Tablets are a new, experimental method of partitioning data among nodes, diverging from vnodes. Individual tablets are now [stored in their own sstables](https://github.com/scylladb/scylladb/commit/bd8bb5d4b157af07949d644626d8c1622b34326d), facilitating data movement and cleanup.

A bug that caused nodes to fail to start if a tablet was migrated concurrently with its table being dropped was [fixed](https://github.com/scylladb/scylladb/commit/1552044615233cafca3d6b1eeaf2e4fc9775d190).

The system.tablets table stores the replica set of each tablet in the system. It now [maintains the order of replicas](https://github.com/scylladb/scylladb/commit/23be6f03360ba4943da55ac5128c7f6398264476), so that the notion of primary owner is maintained.

The scylla.yaml configuration items are now [documented](https://github.com/scylladb/scylladb/commit/e23d9cd7eb55256983462fbd995789312b7ebdb0) in the documentation website.

A recent regression causing a crash on table drop was [fixed](https://github.com/scylladb/scylladb/commit/0f54e24519705691cc58f284e8c1419fb26372f5).

The setup utility supported an --online-discard switch to enable/disable online discard, but it did not actually work. This is now [fixed](https://github.com/scylladb/scylladb/commit/e13a2b687d5caf1d82c863fce5663dc4229cc389).

The `nodetool stop RESHAPE` command is supposed to stop the reshape operation, but in fact only aborted running reshape compactions, which were promptly restarted. It now [aborts](https://github.com/scylladb/scylladb/commit/e0ce711e4fef377a273459871860d6fd599389ab) the entire operation as expected.

A crash during rebuild operations with experimental consistent cluster topology was [fixed](https://github.com/scylladb/scylladb/commit/ce43effc21d36bcae17f55b9141575a27f0d88a3).

ScyllaDB contains two classes of tables, system and user, and uses separate memory pools for their memtables. This avoids a deadlock when a user memtable is being flushed, and needs to allocate memtable space for a system table as part of the flush process. We now [automatically designate](https://github.com/scylladb/scylladb/commit/eb368f9f6e03a6c019fb70c64da7b24a11975547) all system tables as using the system memtable pool.

Latency during repair of large numbers of small rows was [improved](https://github.com/scylladb/scylladb/commit/d944872d19608814c1c63f51c83a61f61c4c0580).

ScyllaDB now supports the [–ignore-dead-nodes option family](https://github.com/scylladb/scylladb/commit/169d19e5b02db4b9ae30227299d35e81717c942e) when experimental consistent cluster topology is enabled.

  

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