Basic Repair Service configuration reference

This reference contains the basic Repair Service options without defaults that can be configured by all customers for their unique environment, such as which tables to include in incremental repairs, or which keyspaces or tables to exclude from subrange repairs. Subrange repairs exclude certain system keyspaces and tables by default. Incremental repairs include certain OpsCenter tables by default. Any tables being repaired incrementally are not subjected to subrange repairs.

The following options are currently configurable by adding a [repair_service] section to the opscenterd.conf file to apply to all clusters, or per cluster by adding the section to the cluster_name.conf file. Settings in cluster_name.conf override any settings in opscenterd.conf. After changing configuration, restart opscenterd.

If there are any issues with the Repair Service configuration, the Repair Service not configured correctly rule in the Best Practice Service fails and provides guidance as to incorrectly configured options, unless the rule has been turned off.

Repair Service Best Practice Rules

Basic configuration for subrange repairs

Flag which keyspaces or tables therein to exclude from subrange repairs:

  • [repair_service] ignore_keyspaces

    The list of keyspaces to ignore during a subrange or distributed subrange repair in addition to system keyspaces.

  • [repair_service] ignore_tables

    The list of keyspace and tables to exclude during a subrange repair. Not applicable to distributed subrange repairs. Example: keyspace1.standard1, keyspace1.standard2.

Basic configuration for distributed subrange repairs

Enable or disable distributed subrange repairs:

  • [repair_service] enable_distributed_subrange_repair

    Specifies whether to enable the Distributed Subrange Repair job type in the Repair Service, which is designed to better scale for large, dense clusters that require an extremely large number of individual subrange repairs. Default: False.

Basic configuration for incremental repairs

Flag which tables or datacenters to include in incremental repairs:

  • [repair_service] incremental_repair_datacenters

    Restricts incremental repairs by datacenters or racks. Setting this option improves performance by limiting the repair requests to only those replicas within the datacenters and any specified racks. Example: dc1,dc2:rack1,dc2:rack2`. The default behavior sends repair requests to all datacenters and racks for all replicas.

  • [repair_service] incremental_repair_tables

    The list of keyspaces and tables to include in incremental repairs. Example: keyspace1.standard1`, keyspace1.standard2.

The OpsCenter.settings and OpsCenter.backup_reports tables are included in incremental repairs by default.

The OpsCenter.settings and OpsCenter.backup_reports tables are flagged as special incremental repair tables in the Table Repair Tasks pane within the Repair Service Status page.

For more information about other incremental config options, see Configuring incremental repairs.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,