Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set covers all product layers, including MOSK management (formerly Container Cloud). This means everything you need is in one place. Some legacy names may remain in the code and documentation and will be updated in future releases. The separate Container Cloud documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Enable Tungsten Fabric Cassandra repairs¶

Available since MOSK 25.1

MOSK enables you to activate automatic Tungsten Fabric database repairs using the tf-dbrepair-job CronJob. Running this repair job is essential for maintaining the health and consistency of a Cassandra cluster.

Below are scenarios where running the repair job is recommended:

Node recovery
If a node has been down for an extended period or replaced, run a repair after bringing it back online to ensure it has all the latest data
Major changes
After significant changes, such as cluster update or schema modifications, run a repair to ensure data consistency
Cluster modifications
When nodes are added or removed, data may not immediately be consistent across replicas. Run a repair to reconcile the data across the cluster

To enable the repair job:

Edit the TFOperator custom resource to enable the database repair job:

spec:
  features:
    dbRepair:
      enabled: true

Optional. Specify the job schedule. By default, the job will run weekly. For example, to schedule the job to run daily:
```
spec:
  features:
    dbRepair:
      enabled: true
      schedule: '@daily'
```
You can also use default cron expressions with five fields. For example, to schedule the job to run at 8:30 on Mondays:
```
spec:
  eatures:
    dbRepair:
      enabled: true
      schedule: '30 8 * * 1'
```