> I do have a hard time buying that an opt-in repair *scheduling* is going to > cause heap problems or impact the daemon significantly; the scheduler > literally reads a few bytes out of a Cassandra table and makes a function > call or two, and then sleeps for 2 minutes.
I wouldn't trivialize it, scheduling can end up dealing with more than a single repair. If theres 1000 keyspace/tables, with 400 nodes and 256 vnodes on each thats a lot of repairs to plan out and keep track of and can easily cause heap allocation spikes if opted in. Chris
