Incremental repairs
Overview of incremental repairs, including considerations and limitations when running and configuring incremental repairs within OpsCenter.
For version 5.1.2, OpsCenter performs an incremental repair on a user-configured set of
tables every time a subrange repair on the mutually exclusive set of other tables is run on a
given node. A user-configurable option (incremental_range_repair
) controls
whether to repair just the subrange or the entire range of the node. The default is to repair
the entire range of the node.
After manually migrating a table to use incremental repair, update the user-configured list
of tables in the incremental_repair_tables
configuration option. Any
incorrectly formatted table logs an error. For more information on migrating to incremental
repairs, see the Cassandra documentation. Read more about efficient
incremental repairs in the DataStax Developer blog post.
Configuration options for incremental repair
The following is 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.
- [repair_service] incremental_repair_tables
- The list of keyspaces and tables to include in incremental repairs. (e.g., Keyspace1.Standard1, Keyspace1.Standard2).
- [repair_service] incremental_range_repair
- Whether incremental repairs should do subrange repair or full repair of a node's entire range.
- [repair_service] incremental_err_alert_threshold
- The threshold for the number of errors during incremental repair to ignore before alerting that incremental repair seems to be failing more than an acceptable amount.