K8ssandra Architecture - Repairs
Apache Cassandra® works tirelessly to provide consistent results for queries. There are a number of anti-entropy mechanisms running constantly to keep data in sync across replicas. Repair is one of these mechanisms. It is recommended that a complete repair cycle is run across the entire dataset once every ten days. In order to reduce the impact of analyzing the entire dataset at once many operators choose to spread out the repair process over the ten day period.
To that end, K8ssandra leverages the excellent Reaper for Apache Cassandra(Reaper) project from The Last Pickle to handle the scheduling, execution, and monitoring of repair tasks. Optionally ingress may be configured as part of the K8ssandra installation for external connectivity to the Reaper web interface.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.