This short report brings to light some interesting commits to scylladb.git master from the last week. Commits in the f4b1ad43d4…e1b1a2068a range are covered.
There were 94 non-merge commits from 23 authors in that period. Some notable commits:
Keyspaces that use tablets now move data by streaming files instead of mutations. This reduces CPU usage and network bandwidth. This feature was ported from ScyllaDB Enterprise.
ScyllaDB can now run on FIPS-compliant operating systems. This feature was ported from ScyllaDB Enterprise.
The version mark in the master branch was updated to 2025.2, indicating the start of the 2025.1 stabilization cycle.
An initialization order problem that could make zstd unavailable for compressing sstables has been fixed.
The nodetool removenode force command was removed. Forcing a removal leaves the cluster in a worse state than it started.
Transport layer security (TLS) uses Linux inotify to watch for certificates changing on disk. It will now consume fewer inotify resources and so have a lesser chance of failing due to that.
Backup will now clean up snapshots as components are uploaded to reduce disk space consumption.
A bug in reading encrypted sstables when their size slightly crosses over the buffer alignment has been fixed.
Audit configuration can now be updated without restarting the server.
Materialized views pair each view replica with a base replica. This pairing is now rack-aware - the database will prefer to pair a base replica and a view replica on the same rack. This reduces rack crossings which can be expensive on public clouds, and generally have lower bandwidth and higher latency.
We now validate PERCENTILE values in speculative_retry schema attributes.
Materialized views with tablets are disabled by default, until the combination is known to work well.
A rare case of materialized view builds never completing was fixed.
See you in the next issue of last week in scylladb.git master!