[RELEASE] ScyllaDB 2025.1.9

Release Notes
, ,
1

The ScyllaDB team announces ScyllaDB 2025.1.9, a bug-fix production-ready patch release for ScyllaDB 2025.1 LTS Release.

Note there is a new Short Term Support (STS) Feature release 2025.3. You are welcome to upgrade to it for the latest and greatest features, or stay on the 2025.1 track for long term support.

Related Links

The following issues are fixed in this release:

Stability

  • Alternator: expression parsing memory leak in specific situations. 25878
  • Enabling a disabled compaction manager throws assertion #24504
  • load_balancer: std::out_of_bounds when decommissioning with empty nodes #26203
  • Revert: undo “auth: move passwords::check call to alien thread” to prevent a case of connection storms from escalating into node crashes #26461

Enhancements & Correctness

  • The batchlog mechanism will now drop batches for a table that was itself dropped #24806
  • Hints are now sent to pending replicas such as tablet migration targets or new nodes #19835
  • PRUNE MATERIALIZED VIEW statement can miss some ghost rows #25655
  • Fixed scrub failures caused by concurrent compactions deleting SSTables before checksum verification. #23363
  • When tablets are split, a compaction process is initiated to break apart SSTables that span the new tablet boundary. This compaction is now prepared for a tablet merge to happen before the split compaction is complete. #24153
  • Changed ignore_nodes from IPs to host IDs to streamline removenode operations. #26228, #26249
  • The tablet scheduler can schedule migrations in different racks independently. It is now more careful not to generate conflicting tablet migration plans. #26038
  • Compaction: reorder operations in compaction_manager::stop to ensure that all compaction executors are stopped and prevent assertion failures. #25806

Alternator

  • Alternator: fixed handling of UpdateItem with a combination of legacy AttributeUpdates and ReturnValues=ALL_OLD. #25894

Optimization

  • Gossiper operations are now enforced to run in the gossip scheduling group, even if invoked from other components #25907
  • The table used for the Raft log now has caching disabled #26027

Tracing and logging

  • Fixed SSTable streaming logs during tablet migration to correctly show the list of files sent, preventing confusion from previously empty file lists. #25830
  • Streaming: Enclose potential throws in try block and ensure sink close before logging #25901, #25497

Performance

  • The tablet load balancer now runs in the maintenance/streaming scheduling group, rather than the gossip group. This reduces impact on node failure detection and Raft which also run in the gossip group #26037

Monitoring

  • S3 Client, used by native backup: Memory Usage Metric – providing visibility into backup and restore memory consumption #25864, #25936