Advanced Repair Service configuration
Reference of available configuration options for the Repair Service. Set the configuration options in either opscenterd.conf or cluster_name.conf. The settings in cluster_name.conf override settings in opscenterd.conf.
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] log_directory
- The location in which to store repair service logs. The default location is /var/log/opscenter/repair_service/ for package installations and install_location/log/repair_service for tarball installations.
- [repair_service] log_length
- Logs will rotate after the specified number of bytes. Defaults to 10485760 (10MB).
- [repair_service] max_rotate
- The maximum number of logs to retain. The default is 10.
- [repair_service] persist_directory
- The location in which to store a file with the current repair service status. The default location is /var/lib/opscenter/repair_service for package installations and install_location/repair_service for tarball installations.
- [repair_service] persist_period
- How often, in seconds, to write the state to the persistence file for the repair service. The default value is 300 (5 minutes).
- [repair_service] restart_period
- How often in seconds to restart repairs. The default value is 300 (5 minutes).
- [repair_service] cluster_stabilization_period
- How often in seconds repair service checks for cluster state before resuming.
- [repair_service] ks_update_period
- The maximum age, in seconds, of a cached version of the current keyspace schema. The default values is 300 (5 minutes).
- [repair_service] single_task_err_threshold
- The number of times to retry a repair task before moving on to the next task. The default value is 10.
- [repair_service] max_err_threshold
- The maximum number of times to fail on a repair before cancelling the repair attempt. Errors during incremental repair do not count towards this threshold. The default value is 100.
- [repair_service] max_parallel_repairs
- The maximum number of repairs to run in parallel. The default value is 0.
- [repair_service] max_pending_repairs
- The maximum pending repairs allowed to be running on a node at one time. The default value is 5.
- [repair_service] alert_on_repair_failure
- Whether there should be alerts fired when a repair task fails. Defaults to true.
- [repair_service] single_repair_timeout
- The maximum length of time for a repair to complete, in seconds. The default value is 3600 (1 hour).
- [repair_service] min_repair_time
- The minimum length of time in seconds for a repair to complete. If a repair finishes sooner it will be padded with a sleep. The default value is 5.
- [repair_service] min_throughput
- The minimum throughput needed to calculate parallel repairs. The default value is 512.
- [repair_service] num_recent_throughputs
- The number of recent throughputs used to calculate the average throughput, which is then used to determine how many parallel repairs are needed. The default value is 20.
- [repair_service] error_logging_window
- The desired amount of time in seconds between errors for exceeding max_parallel_repairs. Defaults to 86400
- [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.
- [repair_service] snapshot_override
- Specifies whether to override the default snapshot repair behavior. The default value is False. Specifying this option as either True or False will always modify the behavior of the repair service. Snapshot repair can only be configured for Cassandra versions 2.0.11 and greater.
opscenterd.conf
The location of the opscenterd.conf file depends on the type of installation:
- Installer-Services or package installations: /etc/opscenter/opscenterd.conf
- Installer-No Services or tarball installations: install_location/conf/opscenterd.conf
- Windows installations: Program Files (x86)\DataStax Community\opscenter\conf\opscenterd.conf
cluster_name.conf
The location of the cluster_name.conf file depends on the type of installation:
- Installer-Services or package installations: /etc/opscenter/clusters/cluster_name.conf
- Installer-No Services or tarball installations: install_location/conf/clusters/cluster_name.conf
- Windows installations: Program Files (x86)\DataStax Community\opscenter\conf\clusters\cluster_name.conf