Not sure if incremental repair option is getting passed accidentally

BrianGallew / cassandra_range_repair

python script to repair the primary range of a node in N discrete steps

MIT License

109 stars 47 forks source link

Not sure if incremental repair option is getting passed accidentally #49

Open atinsood opened 8 years ago

atinsood commented 8 years ago

On a 3.x cluster even without asking for incremental repair using

./range_repair.py -k odin -l -v

I still keep seeing this message as warning in the logs.

RepairOption.java:148 - Incremental repair can't be requested with subrange repair because each subrange repair would generate an anti-compacted table. The repair will occur but without anti-compaction.

BrianGallew commented 8 years ago

None of this scripting has been tested against 3.x.

powellchristoph commented 8 years ago

Incremental repairs are the default in 3.X.

atinsood commented 8 years ago

Thanks @BrianGallew @powellchristoph I can give it a spin against 3.x and see how thins work out. w.r.t. incremental repairs being default in 3.x, are you guys aware if incremental repairs and range repairs are not compatible with each other or is the above warning pretty much telling you that basically I am preventing something bad from happening.