The ScyllaDB team announces the release of ScyllaDB Manager 3.5.1, a production-ready patch release of the stable 3.5 branch.
ScyllaDB Manager is a centralized cluster administration and recurrent tasks automation tool.
This release focuses on many important bugfixes.
Bug Fixes
- Increase the timeout on describe ring API call (#4482)
- Make local query instead of scan in healthcheck CQL ping (#4329)
- Respect
backup --skip-schema
flag (#4468) - Fix snaphost tag collision for a single ScyllaDB Manager instance (#3873)
- Fix restore batch mechanism which caused partial restore on retry (#4344)
- Don’t timeout on repair status and restore load&stream calls (#4419)
- Don’t long poll tablet repair status as it causes sporadic http error 400 (#4434)
- Fix race condition when client call finished when context was cancelled (#3848)
- Align restore bandwidth reported in
sctool progress
and metrics (#4358) - Populate
scylla_manager_repair_progress
metric (#4448) - Don’t return deleted task in manager client (#4400)
Upgrade to the new release
ScyllaDB customers are encouraged to upgrade to ScyllaDB Manager 3.5.1 in coordination with the ScyllaDB support team.
The new release includes upgrades of both ScyllaDB Manager Server and Agent.
Useful Links:
- Download ScyllaDB Manager and ScyllaDB Manager Agent for ScyllaDB customers
- Download ScyllaDB Manager and ScyllaDB Manager Agent for regular users
- ScyllaDB Manager container instance and example
- ScyllaDB Manager 3.5 documentation
- Upgrade from ScyllaDB Manager 3.5.0 to ScyllaDB Manager 3.5.1
- Submit a ticket for questions or issues with Manager 3.5.1 (ScyllaDB customers)
Scylla Manager 3.5.1 supports the following ScyllaDB releases:
- 2025.2
- 2025.1
- 2024.2
- 2024.1
- You can install and run ScyllaDB Manager on Kubernetes using ScyllaDB Operator. More here.