Re: repair in C* 3.11.2 and anticompactions

Jean, Have you considered nodetool repair -pr (primary range) OR reaper? With Reaper you can throttle repair load on system. These two uses ranges anyway, so you may not run into anti-compaction. Regards, Nitan K. Cassandra and Oracle Architect/SME Datastax Certified Cassandra expert Oracle 10g

Re: repair in C* 3.11.2 and anticompactions

Thanks alain and Lerh, It is clear now. In order to avoid problems and charge in the cluster doing anticompactions, I am going to use repair by sub ranges. I studied this tool called cassandra-list-subranges it seems it still works for

Re: repair in C* 3.11.2 and anticompactions

Hi Jean, Here is what Alexander wrote about it, a few months ago, in the comments of the article mentioned above: "A full repair is an incremental one that doesn't skip repaired data. > Performing anticompaction in that case too (regardless it is a valid > approach or not) allows to mark as repai

Re: repair in C* 3.11.2 and anticompactions

Hey Jean, I think it still does anticompaction by default regardless, it will not do so only if you do subrange repair. TLP wrote a pretty good article on that: http://thelastpickle.com/blog/2017/12/14/should-you-use-incremental-repair.html On 24 May 2018 at 00:42, Jean Carlo wrote: > Hello > >

repair in C* 3.11.2 and anticompactions

Hello I just want to understand why, if I run a repair non incremental like this nodetool -h 127.0.0.1 -p 7100 repair -full -pr keyspace1 standard1 Cassandra does anticompaction as the logs show INFO [CompactionExecutor:20] 2018-05-23 16:36:27,598 CompactionManager.java:1545 - Anticompacting [