Re: Incremental repairs in 3.0

Hi Paulo! Sorry there was something I was doing wrong. Now I can see that the value of Repaired At changes even if there is no streaming. I am using cassandra 2.1.14 and the comand was nodetool repair -inc -par. Anyway good to know this: > If you're using subrange repair, please note that this

Re: Incremental repairs in 3.0

> I truncate a table lcs, Then I inserted one line and I used nodetool flush to have all the sstables. Using a RF 3 I ran a repair -inc directly and I observed that the value of Reaired At was equal 0. Were you able to troubleshoot this? The value of repairedAt should be mutated even when there

Re: Incremental repairs in 3.0

Well I did an small test on my cluster and I didn't get the results I was expecting. I truncate a table lcs, Then I inserted one line and I used nodetool flush to have all the sstables. Using a RF 3 I ran a repair -inc directly and I observed that the value of Reaired At was equal 0. So I start

Re: Incremental repairs in 3.0

HI Jean, This blog post is a pretty good resource: http://www.datastax.com/dev/blog/anticompaction-in-cassandra-2-1 I believe in 2.1.x you don't need to do the manual migration procedure, but if you run regular repairs and the data set under LCS is fairly large (what this means will probably

Re: Incremental repairs in 3.0

Thanks for answer! >It may still be a good idea to manually migrate if you have a sizable amount >of dataNo, it would be brand new ;-) 3.0 cluster On Tuesday, June 21, 2016 1:21 AM, Bryan Cheng wrote: Sorry, meant to say "therefore manual migration procedure

Re: Incremental repairs in 3.0

Sorry, meant to say "therefore manual migration procedure should be UNnecessary" On Mon, Jun 20, 2016 at 3:21 PM, Bryan Cheng wrote: > I don't use 3.x so hopefully someone with operational experience can chime > in, however my understanding is: 1) Incremental repairs

Re: Incremental repairs in 3.0

I don't use 3.x so hopefully someone with operational experience can chime in, however my understanding is: 1) Incremental repairs should be the default in the 3.x release branch and 2) sstable repairedAt is now properly set in all sstables as of 2.2.x for standard repairs and therefore manual

Incremental repairs in 3.0

Hi, assuming I have new, empty Cassandra cluster, how should I start using incremental repairs? Is incremental repair is default now (as I don't see -inc option in nodetool) and nothing is needed to use it, or should we perform migration procedure anyway? And what happens to new column