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
> 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 is
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 t
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 depe
Hi @Bryan
When you said "sizable amount of data" you meant a huge amount of data
right? Our big table is in LCS and if we use the migration process we will
need to run a repair seq over this table for a long time.
We are planning to go to repairs inc using the version 2.1.14
Saludos
Jean Carlo
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 should be
UNnecessary"
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 should be the
> default in t
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
migr
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 families?
