cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean Carlo <jean.jeancar...@gmail.com>
Subject repair in C* 3.11.2 and anticompactions
Date Wed, 23 May 2018 14:42:23 GMT
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
[BigTableReader(path='/home/jriveraura/.ccm/test/node1/data0/keyspace1/standard1-36a6ec405e9411e8b1d1b38a73559799/mc-2-big-Data.db')]

As far as I understood the anticompactions are used to make the repair
incremantals possible, so I was expecting no having anticompactions making
repairs with the options  -pr -full

Anyone knows why does cassandra make those anticompactions ?

Thanks

Jean Carlo

"The best way to predict the future is to invent it" Alan Kay

Mime
View raw message