https://github.com/mstump/cassandra_range_repair
Also very useful. Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359 On 22/08/2014, at 6:12 AM, Robert Coli <rc...@eventbrite.com> wrote: > On Thu, Aug 21, 2014 at 12:32 PM, Kevin Burton <bur...@spinn3r.com> wrote: > How do I watch the progress of nodetool repair. > > This is a very longstanding operational problem in Cassandra. Repair barely > works and is opaque, yet one is expected to run it once a week in the default > configuration. > > An unreasonably-hostile-in-tone-but-otherwise-accurate description of the > status quo before the re-write of streaming in 2.0 : > > https://issues.apache.org/jira/browse/CASSANDRA-5396 > > A proposal to change the default for gc_grace_seconds to 34 days, so that > this fragile and heavyweight operation only has to be done once a month : > > https://issues.apache.org/jira/browse/CASSANDRA-5850 > > granted , this is a lot of data, but it would be nice to at least see some > progress. > > Here's the rewrite of streaming, where progress indication improves > dramatically over the prior status quo : > > https://issues.apache.org/jira/browse/CASSANDRA-5286 > > And here's two open tickets on making repair less opaque (thx > yukim@#cassandra) : > > https://issues.apache.org/jira/browse/CASSANDRA-5483 > https://issues.apache.org/jira/browse/CASSANDRA-5839 > > =Rob > >
