> Assuming the situation is just "we accidentally ran incremental repair", you
> shouldn't have to do anything. It's not going to hurt anything
Once you run incremental repair, your data is permanently marked as
repaired, and is no longer compacted with new non-incrementally
repaired data. This c
The following presentation describes in detail a technique for using
coordinator-only nodes which will give you similar behavior (particularly
slides 12 to 14):
https://www.slideshare.net/DataStax/optimizing-your-
cluster-with-coordinator-nodes-eric-lubow-simplereach-cassandra-summit-2016
On Thu,
Thanks Blake and Paulo for the response.
Yes, the idea is to go back to non incremental repairs. I am waiting for all
the "anticompaction after repair" activities to complete and in my
understanding( thanks to Blake for the explanation ), I can run a full repair
on that KS and then get back to
Yes mark them as unrepaired first. You can get sstablerepairedset from
source if you need (probably make sure you get the correct branch/tag).
It's just a shell script so as long as you have C* installed in a
default/canonical location it should work.
https://github.com/apache/cassandra/blob/trunk/
Hi Everyone,
We need some help in deciding whether to use User Defined Type(UDT) nested
in LIST collection columns in our table.
In a couple of months, we are planning to roll out a new solution that will
incorporate a Read heavy use case.
We have one big table which will hold around 250 million
