On Fri, May 2, 2014 at 12:29 AM, Jan Kesten <j...@dg6obo.de> wrote: > I'm running a cassandra cluster with 2.0.6 and 6 nodes. As far as I know, > routine repairs are still mandatory for handling tombstones - even I > noticed that the cluster now does a "snapshot-repair" by default. > > Now my cluster is running a while and has a load of about 200g per node - > running a "nodetool repair -pr" on one of the nodes seems to run forever, > right now it's running for 2 complete days and does not return. >
https://issues.apache.org/jira/browse/CASSANDRA-5220 The reports I am getting on this list and in #cassandra about the newly re-written repair in 2.0.x line, with vnodes on a real sized data set, is that it often does not work, and if it does work, not in tractable time. As other posters have said, it is continually being fixed and improved. If I were you, I would consider increasing gc_grace_seconds to something like 34 days until repair starts working more efficiently with vnodes. https://issues.apache.org/jira/browse/CASSANDRA-5850 =Rob
