Searching for results...

No results

Your search did not match anything from Mirantis documentation.
Check your spelling or try different keywords.

An error occurred

An error occurred while using the search.
Try your search again or contact us to let us know about it.

Newer documentation is now live.You are currently reading an older version.

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:

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

    spec:
  features:
    dbRepair:
      enabled: true

  2. 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'

See also