This short report brings to light some interesting commits to scylladb.git master from the last week. Commits in the f744007e136…5880a1b90b4 range are covered.
There were 67 non-merge commits from 16 authors in that period. Some notable commits:
The TRUNCATE operation has been promoted to a topology level operation. This allows the topology change coordinator to drive the operation to completion in the face of node failures and concurrent tablet migrations.
ScyllaDB now leaves some Linux aio control blocks for use of native tooling such as the scylla sstable command. Linux aio control blocks are a limited resource and can prevent tool start up when exhausted. As part of that change the io_uring Seastar backend was enabled (as a non-default backend).
Commitlog replay fixes a corner case where a shard that received no mutations before crashing had its commitlog interpreted incorrectly.
When decommissioning a node in a cluster that has different shard counts per node, we are now more careful to preserve tablet balance among the remaining nodes.
Tablet migrations are now surfaced as tasks that can be observed and controlled by the nodetool tasks command family.
See you in the next issue of last week in scylladb.git master!