[RELEASE] ScyllaDB Manager 3.11.1

Release Notes
, ,
1

The ScyllaDB team announces the release of ScyllaDB Manager 3.11.1, a production-ready patch release of the stable 3.11 branch.

ScyllaDB Manager is a centralized cluster administration and recurrent tasks automation tool.

This release focuses on bug fixes, setup script updates, and other improvements.

Below are the changes in this release.

Recognize new mt SSTable format (#4845)

ScyllaDB is introducing a new mt SSTable format which supersedes the ms format. As ScyllaDB Manager needs to recognize the format of SSTables handled during backup and restore procedures, this ensures forward compatibility between next ScyllaDB Manager and ScyllaDB releases.

Make backup permission check safe to run in parallel (#4852)

Changes introduced to backup permission check procedure in ScyllaDB Manager 3.11.0 made it not safe to execute it in parallel for the same cluster. Those permissions are checked when adding, updating, dry-running or running backup task. Executing any combination of these operations in parallel could have resulted in an error (note that ScyllaDB Manager scheduler allows for only a single backup task execution per cluster at any given time).

Update default ScyllaDB Manager backend DB setup (#4853)

Running scyllamgr_setup script configured local ScyllaDB node serving as the ScyllaDB Manager backend. This configuration was updated in the following way:

  • increased memory from 500MB to 1GB

  • disabled auto_snapshot ScyllaDB feature

Low ScyllaDB Manager DB memory could result in degraded performance (especially during intensive repair of vNode keyspaces).
As ScyllaDB Manager DB does not store user data, the auto_snapshot feature is not needed and could result in accumulating disk space usage after maintenance operations such as restoring ScyllaDB Manager DB contents.

Note that this is only the default ScyllaDB Manager DB configuration - it can be adjusted manually to fit the specific needs of a given deployment.

Drop ownership of scylla-helper.slice configuration (#4854)

In previous releases, running scyllamgr_agent_setup script during ScyllaDB Manager Agent installation and upgrade procedures configured scylla-helper.slice under /etc/systemd/system. This scylla-helper.slice configuration overrode the ScyllaDB node configuration placed under /usr/lib/systemd/system.

Maintaining this configuration on both ScyllaDB Manager Agent and ScyllaDB node sides increases the risk of misconfiguration of scylla-helper.slice. Because of that, scyllamgr_agent_setup no longer configures scylla-helper.slice even when –no-scylla-helper-slice=false. Instead, it validates that the ScyllaDB node configuration is present and removes any previous ScyllaDB Manager Agent configuration files.

Other changes:

  • Run full tablet repair after restore explicitly (#4847)

  • Reverted gocql from 1.18.0 to 1.15.3 over change in dialing logic (#4860)

Upgrade to the new release

ScyllaDB customers are encouraged to upgrade to ScyllaDB Manager 3.11.1 in coordination with the ScyllaDB support team.

The new release includes upgrades of both ScyllaDB Manager Server and Agent.

Useful Links:

ScyllaDB Manager 3.11.1 supports the following ScyllaDB releases

  • 2026.2

  • 2026.1

  • 2025.4

  • 2025.1

You can install and run ScyllaDB Manager on Kubernetes using ScyllaDB Operator. More here.