Running Repairs
Repairs are a critical anti-entropy operation in Cassandra. In the past, there have been many custom solutions to manage them outside of your main Cassandra Installation. In K8ssandra, there is a tool called Reaper (contributed by Spotify and developed by TLP) that eliminates the need for a custom solution. Just like K8ssandra makes Cassandra setup easy, Reaper makes configuration of repairs even easier.
✅ Step 1: Check the cluster’s health
Navigate to your cloud instance link list and click on reaper or use the http://repair.<YOURADDRESS>:8080/webui/ link
If you are running this locally then navigate to repair.localhost:8080/webui/
Notice the way that 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.
✅ Step 2: Schedule a cluster repair
On the left hand side, notice the schedule menu option.
Click Schedule
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 deletion.
Notice the new repair added to the list.
✅ Step 3:Run a cluster repair
On the repair job you just configured, click the Run now button.
Notice the repair job kicking off.
For more reading on Reaper, visit this link
Amazing work! Now go to the github repo and submit your assignment! You did a good job so let us proof it with your "K8ssandra Workshop" achievement unlocked!