[RELEASE] ScyllaDB Manager 3.12.1

Release Notes
, ,
1

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

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

This release contains two important repair task bug fixes.

Below are the changes in this release.

VNode tables repaired with small table optimization are not fully repaired (#4911)

ScyllaDB Manager general purpose repair task utilizes ScyllaDB small table optimization for repairing VNode tables smaller than –small-table-threshold.
ScyllaDB Manager was mistakenly limiting the scope of such repair to an arbitrary replica set of repaired table.
For tables which are not replicated on all nodes, this resulted in not repairing table’s entire dataset.

This could cause different issues depending on table’s tombstone_gc mode:

  • repair - tombstone accumulation (such accumulation would make the table go over –small-table-threshold, which would cause it to be fully repaired and allowed for compacting accumulated tombstones away)

  • timeout - data resurrection

ScyllaDB Manager 3.12.1 addresses this issue and ensures that VNode tables are fully (according to set filtering options like –dc) repaired when using ScyllaDB small table optimization.

Tablet tables repair does not advance repaired_at timestamp (#4911)

After successful repair of tablet table’s entire dataset, ScyllaDB advances table’s repaired_at timestamp.
This timestamp is not advanced on partial repairs, which are defined by ScyllaDB tablet repair requests with any filtering parameters set - even is such parameters do not result in filtering anything out.
ScyllaDB Manager general purpose repair task was always setting data center filtering parameter in the ScyllaDB tablet repair requests - even when no ScyllaDB Manager repair flag (e.g., –dc) was used.

This made impact on features relying on table’s repaired_at timestamp:

  • tablet incremental repair - data is repaired from scratch as if tablet incremental repair was not used

  • tombstone_gc mode repair - tombstone accumulation

ScyllaDB Manger 3.12.1 addresses this issue and ensures that no unnecessary filtering parameters are set in ScyllaDB tablet repair request.
ScyllaDB Manager tablet repair task was not affected by this issue.

Upgrade to the new release

ScyllaDB customers are encouraged to upgrade to ScyllaDB Manager 3.12.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.12.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.