I know it doesn't. But is this a valid enhancement request?
Currently Cassandra does not run repair automatically. You can use cron and 'nodetool repair' as a simple approach.On Tue, Jul 5, 2011 at 1:27 PM, Raj N <firstname.lastname@example.org> wrote:
Are there any benchmarks that quantify how long nodetool repair takes? Something which says on this kind of hardware, with this much of data, nodetool repair takes this long. The other question that I have is since Cassandra recommends running nodetool repair within GCGracePeriodSeconds, is it possible to introduce a setting in cassandra.yaml, that allows you to specify the frequency of nodetool repair so that Cassandra can itself determine when to run nodetool repair instead of setting up a cron job. Since Cassandra knows about all its peers, it can be smart enough to also decide which nodes can run repair concurrently. For example, if RF =3, and I have 6 nodes, then 2 replicas which are responsible for different ranges in the ring can run repair concurrently.