[RELEASE] ScyllaDB 2025.1.7

Release Notes
, ,
1

The ScyllaDB team announces ScyllaDB 2025.1.7, 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

  • service/qos: Modularize service level controller to avoid invalid access to a stopped auth::service #24792

  • Commitlog: segment_manager::discard_unused_segments - separate the modification of the vector (_segments) from actual releasing of objects #25709

  • Drop table during tablet cleanup initiated by a tablet migration may crash #25706

  • gossiper - race condition in gossip::apply_state_locally when receiving messages containing removed endpoints that no longer have a valid host id #25702, #25621

  • gossiper can reply with an empty self host id in `gossip_get_endpoint_states_response` during startup #25831

  • Tablets Repair: A node may crash If a node has many shards and many tablets on each shard #23632

  • Segmentation fault in scheduling group streaming during tablets streaming after node was decommissioned #23162

Optimization

  • Improved handling of in-progress requests during node shutdown, ensuring requests are allowed to complete successfully. #24481

  • Removed a large allocation when loading SSTables #3335

  • raft_sys_table_storage: avoid an extra copy when deserializing log_entry #23903,

  • seastar_memory - Removed an oversized allocation changing token_range_vectorto use chunked_vector #24156, #24115

  • storage_service::maybe_reconnect_to_preferred_ip() calls the gossiper::get_host_id() unnecessarily and can be passed directly as a parameter #25715

  • Optimized container footprint – The container image size has been minimized to improve efficiency #25479

Tracing and logging

  • Backport ‘reactor: Update seastar submodule to get more info and robustness on segfault’ scylladb#25681

  • db/hints: Improve logs #25466

  • Debug logs: deletion_time formatter prints wrong results #25556

  • db/commitlog: Extend error messages for corrupted data #25459

API and tooling

  • Warn users about using RF!=Racks with Tablets Keyspaces #23330

  • storage_service/get_natural_endpoints has no way to pass a key containing a colon character #24829

Performance

  • Alternator, ScyllaDB’s implementation of the DynamoDB API, is now more careful to avoid large contiguous allocations during query/scan operations, as these can cause stalls. #23535

  • Improve performance of worst case scenario in auth::passwords::detail::hash_with_salt #24524

  • Improve performance for partial repair with a node down and with many tablets #22413

  • storage_service: on_change: frequent system.peers reloads with many peers may cause high CPU usage #25660

  • system_keyspace::drop_truncation_rp_records can cause unbound parallelism #25682