The ScyllaDB team is pleased to announce the release of ScyllaDB 2025.3.1, a production-ready path release for ScyllaDB 2025.3 Feature Release.
Related Links
The following issues are fixed in this release:
Correctness
- storage_service/get_natural_endpoints has no way to pass a key containing a colon character #24829
Stability
- Alternator: character 0x255 in base64 causes out-of-bounds read #25701
- 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
- service/qos: Modularize service level controller to avoid invalid access to a stopped auth::service #24792
Optimization
- Dropped tables should be removed from system.truncated #25683
- Improved handling of in-progress requests during node shutdown, ensuring requests are allowed to complete successfully. #24481
- storage_service::maybe_reconnect_to_preferred_ip() calls the gossiper::get_host_id() unnecessarily and can be passed directly as a parameter #25715
Performance
- 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
Tooling - system_keyspace::drop_truncation_rp_records can cause unbound parallelism #25682
Log and trace