This short report brings to light some interesting commits to scylladb.git master from the last week. Commits in the 29c2d4e7eb…e7d6ab576b range are covered.
There were 55 non-merge commits from 16 authors in that period. Some notable commits:
The system.peers table was continuously updated even if no change was happening, stressing the disk. This is now fixed.
Materialized views perform a read operation on the base table before writing the the view table. This read operation now has better concurrency control: the amount of memory consumed by reads is limited, and when the CPU is the bottleneck, we avoid issuing new reads to avoid flooding the system with competing operations.
When using S3, we upload files in chunks. We now recover those chunks on error and delete them.
The sstable reader will now consult data in memtable before purging tombstones. This prevents data resurrection in scenarios involving very low write activity, which can lead to data staying in memtables for longer than a repair cycle.
Data definition language (DDL) statements are automatically retried in case of an internal race accessing Raft. A crash during this retry, for ALTER KEYSPACE statements, was fixed.
See you in the next issue of last week in scylladb.git master!