Repairs are a critical anti-entropy operation in Apache Cassandra®. In the past, there have been many custom solutions to manage them outside of your main Cassandra Installation. K8ssandra provides the Repair Web Interface (also known as Cassandra Reaper) that eliminates the need for a custom solution. Just like K8ssandra makes Cassandra setup easy, Reaper makes configuration of repairs even easier.
Note: The requirement for your environment may vary considerably, however the general recommendation is to run a repair operation on your Cassandra clusters about once a week.
- Web Browser
- values.yaml configuration, or use
--setflags on the command line
- Kubernetes cluster with the following elements deployed:
- DNS name configured for the repair interface, referred to as REPAIR DOMAIN below.
Access Repair Interface
With the prerequisites satisfied the repair GUI should be available at the following address:
For example, to upgrade a previously installed
k8ssandra that’s running locally:
helm upgrade k8ssandra k8ssandra/k8ssandra --set ingress.traefik.enabled=true --set ingress.traefik.repair.host=repair.localhost
Notice how in this example, the DNS host name is specified on the command line as
After a few minutes, check that the pods are running. Example:
kubectl get pods NAME READY STATUS RESTARTS AGE cass-operator-86d4dc45cd-pgcs8 1/1 Running 0 12m grafana-deployment-6bb9bc6d89-ghc4s 1/1 Running 0 4m8s k8ssandra-dc1-default-sts-0 2/2 Running 0 4m48s k8ssandra-tools-grafana-operator-k8ssandra-54fbbc799c-68htn 1/1 Running 0 12m k8ssandra-tools-kube-prome-operator-f87955c85-t2s9k 2/2 Running 0 12m k8ssandra-reaper-k8ssandra-64b6b4c58-mkfxw 1/1 Running 0 2m52s k8ssandra-reaper-operator-k8ssandra-799bd4568f-lk4hv 1/1 Running 0 4m49s prometheus-mycluster-prometheus-k8ssandra-0 3/3 Running 1 4m48s
What can I do in Reaper?
To access Reaper, if you are running locally, navigate to http://repair.localhost:8080/webui/.
Check the cluster’s health
In the Reaper UI, notice how the nodes are displayed inside the datacenter for the cluster.
The color of the nodes indicates the overall load the nodes are experiencing at the current moment.
Schedule a cluster repair
On the UI’s left sidebar, notice the Schedule option.
Click Add schedule and fill out the details when you are done click the final add schedule to apply the new repair job. A Cassandra best practice is to have one repair complete per week to prevent zombie data from coming back after a deletion.
Notice the new repair added to the list.
Run a cluster repair
On the repair job you just configured, click Run now.
Notice the repair job kicking off.
See Run a cluster repair.
For more reading on Reaper, visit this article on medium.com.
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.