Cassandra keeps copies of data on different servers, and those copies can need repair to bring them back into agreement. Reaper schedules and coordinates that repair work, divides it into manageable pieces, and shows progress so operators do not have to run every repair manually. It is useful for making this recurring database task visible and controlled. Repair reconciles replicas; it is not a backup that recovers accidentally deleted data.
Deployment and operating notes
The current Reaper documentation describes segmented repair, back-pressure handling, pause and cancellation controls, scheduling and a REST interface. It also documents deployment backends, authentication and Cassandra compatibility. The historical description still identifies the right tool, but an old chart or image should not decide the version used with a current Cassandra cluster.
Choose Reaper and its storage backend according to the Cassandra version and deployment model, including whether an operator already manages it. Inventory existing repair schedules, credentials and repair history before replacing an instance. Avoid accidentally running overlapping repair coordinators against the same keyspaces. Validate JMX or management connectivity, repair completion and compaction pressure on a limited scope before expanding scheduling. Compare the repair interval with the database’s deletion and consistency requirements rather than copying another cluster’s timer. Preserve Reaper configuration separately from Cassandra data backups: repair reconciles replicas, while backup recovery addresses data loss. An accessible Reaper UI is not evidence that repair jobs are succeeding.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2019-05-10T06:04:16+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
Reaper is an open source tool that aims to schedule and orchestrate repairs of Apache Cassandra clusters.
It improves the existing nodetool repair process by
- Splitting repair jobs into smaller tunable segments.
- Handling back-pressure through monitoring running repairs and pending compactions.
- Adding ability to pause or cancel repairs and track progress precisely.
Reaper ships with a REST API, a command line tool and a web UI.
The post Cassandra Reaper appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →