# Last week in scylladb.git master (issue #200; 2023-10-08)

**URL:** <https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-200-2023-10-08/897>\
**Category:** ScyllaDB\
**Tags:** git-news\
**Created:** [October 8, 2023, 6:23pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-200-2023-10-08/897 "2023-10-08T18:23:46Z")\
**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:** [October 8, 2023, 6:23pm UTC](https://forum.scylladb.com/t/last-week-in-scylladb-git-master-issue-200-2023-10-08/897/1 "2023-10-08T18:23:46Z")

</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 1640f83fdc…4e6fe34501 range are covered.

There were 139 non-merge commits from 14 authors in that period. Some notable commits:

  

The native implementation of nodetool supports [many more commands](https://github.com/scylladb/scylladb/commit/d217c6f7c14420b17cd739dbdcae97090305794b). Note it’s not yet part of regular nodetool invocation.

Tablets are a new, experimental method of distributing data in a ScyllaDB cluster. With tablets, data movement is decoupled from node bootstrap and decommissioning. When a tablet is migrated, its sstables will now be automatically [cleaned up](https://github.com/scylladb/scylladb/commit/1252d5bd7ddd86f6fe21d51fc8930447a42afda9) on the source node.

The log-structured allocator (LSA) will evict cache if a query fails because it needs more memory, and retry it. On the other hand, the reader concurrency semaphore will simulate an allocation failure to a query if it detects the system is under severe memory pressure. The two mechanisms work against each other, as we’ll simulate an allocation failure in order to terminate a query, but LSA will respond by retrying it. To avoid this, LSA will now [detect](https://github.com/scylladb/scylladb/commit/e600f35d1e217c88851486f2de5110fe4564047a) the simulated allocation failure and let the query be terminated.

A `map<ascii, something>` value, when parsed from its JSON representation, did not parse the key correctly. This is now [fixed](https://github.com/scylladb/scylladb/commit/75109e9519dcbefe6554593619bacaa598ea0259).

If a QUORUM (or higher) read detects a mismatch between data from different replica, it starts a process of reconciliation to bring all replicas to the same state. Previously, this did not work well when at least on replica had a large prefix of tombstones, as we would read all of them into memory. Now, we are able to [incrementally process sections](https://github.com/scylladb/scylladb/commit/854188a486142be4dd9ba51c388bdc9add69fc17) of the data, even if they are all tombstones.

  

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