If you are on 2.1.2+ (or using STCS) you don't those steps (should probably update the blog post).
Now we keep separate levelings for the repaired/unrepaired data and move the sstables over after the first incremental repair But, if you are running 2.1 in production, I would recommend that you wait until 2.1.3 is out, https://issues.apache.org/jira/browse/CASSANDRA-8316 fixes a bunch of issues with incremental repairs -pr is sufficient, same rules apply as before, if you run -pr you need to repair every node /Marcus On Thu, Jan 8, 2015 at 9:16 AM, Roland Etzenhammer < r.etzenham...@t-online.de> wrote: > Hi, > > I am currently trying to migrate my test cluster to incremental repairs. > These are the steps I'm doing on every node: > > - touch marker > - nodetool disableautocompation > - nodetool repair > - cassandra stop > - find all *Data*.db files older then marker > - invoke sstablerepairedset on those > - cassandra start > > This is essentially what http://www.datastax.com/dev/ > blog/anticompaction-in-cassandra-2-1 says. After all nodes migrated this > way, I think I need to run my regular repairs more often and they should be > faster afterwards. But do I need to run "nodetool repair" or is "nodetool > repair -pr" sufficient? > > And do I need to reenable autocompation? Oder do I need to compact myself? > > Thanks for any input, > Roland >
