The ScyllaDB team announces the release of ScyllaDB Manager 3.2.4 production-ready ScyllaDB Manager patch release of the stable ScyllaDB Manager 3.2 branch.
ScyllaDB Manager is a centralized cluster administration and recurrent tasks automation tool.
This release fixes issues in Manager backup, in particular for Alternator, and repair.
- Scylla Manager 3.2.4, addresses an issue where users encountered errors during the final stage of backup, specifically in purging old snapshots (#3615).
- proper support for Alternator keyspaces backups within the scylla-manager backup feature (#3165).
- An enhanced the UI by including information about the intensity and parallelism used in a particular repair run (#3621).
- Starting with the 3.2.4 release, the manager now skips the system_distributed.cdc_generation_descriptions table from the default set of keyspaces used in the repair task (#3601).
- Ability to override the default 9042 CQL port for the Scylla backend used by Scylla Manager (#3580).
In addition to linux/amd64 images, we’ve begun publishing linux/arm64 docker images for scylla-manager and scylla-manager-agent (#3278).
For a comprehensive list of commits included in the 3.2.4 release, please refer to this link.
ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Manager 3.2.4 in coordination with the ScyllaDB support team.
The new release includes upgrades of both ScyllaDB Manager Server and Agent.
- Scylla Manager 3.2 Release Notes
- Download ScyllaDB Manager and ScyllaDB Manager Agent for ScyllaDB Enterprise customers
- Download ScyllaDB Manager and ScyllaDB Manager Agent for open source users (up to 5 nodes)
- ScyllaDB Manager Docker instance and example
- ScyllaDB Manager 3.2 documentation
- Upgrade from ScyllaDB Manager 3.2.0 to ScyllaDB Manager 3.2.4
- Submit a ticket for questions or issues with Manager 3.2.4 (ScyllaDB Enterprise users)
Scylla Manager 3.2.4 support the following Scylla Enterprise releases:
And the following Open Source release (limited to 5 nodes see license):
You can install and run Scylla Manager on Kubernetes using Scylla Operator. More here.