The ScyllaDB team announces the release of ScyllaDB Manager 3.9.1, a production-ready patch release of the stable 3.9 branch.
ScyllaDB Manager is a centralized cluster administration and recurrent tasks automation tool.
This release focuses on bug fixes and dependencies upgrades.
Below are the changes in this release.
Incorrect parsing of sctool backup flags with multiple entries (#4714)
This bug caused issues when running sctool backup <delete|files|list> commands with multiple entries for –location, –snapshot-tags or –keyspace flags. This forced users to execute those commands one by one.
SM server startup fails on non default SM DB port (#4801)
Even though it was possible to specify custom port used for communication with ScyllaDB Manager backend ScyllaDB cluster (database.port in scylla-manager.yaml), ScyllaDB Manager still executed initial configuration CQL queries against the default 9042 port. This resulted in ScyllaDB Manager server startup failure when the 9042 port was not exposed.
Other updates
- Bumped grpc package - google.golang.org/grpc - Go Packages from 1.56.3 to 1.79.3 (#4797)
Upgrade to the new release
ScyllaDB customers are encouraged to upgrade to ScyllaDB Manager 3.9.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.9 documentation
- Upgrade from ScyllaDB Manager 3.8 to ScyllaDB Manager 3.9.1
- Submit a ticket for questions or issues with ScyllaDB Manager 3.9.1 (ScyllaDB customers)
ScyllaDB Manager 3.9.1 supports the following ScyllaDB releases
- 2026.1
- 2025.4
- 2025.3
- 2025.1
- 2024.1
You can install and run ScyllaDB Manager on Kubernetes using ScyllaDB Operator. More here.