Welp, that's good but wasn't apparent in the codebase :S. Kurt Greaves k...@instaclustr.com www.instaclustr.com
On 20 October 2016 at 05:02, Alexander Dejanovski <a...@thelastpickle.com> wrote: > Hi Kurt, > > we're not actually. > Reaper performs full repair by subrange but does incremental repair on all > ranges at once, node by node. > Subrange is incompatible with incremental repair anyway. > > Cheers, > > On Thu, Oct 20, 2016 at 5:24 AM kurt Greaves <k...@instaclustr.com> wrote: > >> >> On 19 October 2016 at 17:13, Alexander Dejanovski <a...@thelastpickle.com >> > wrote: >> >> There aren't that many tools I know to orchestrate repairs and we >> maintain a fork of Reaper, that was made by Spotify, and handles >> incremental repair : https://github.com/thelastpickle/cassandra-reaper >> >> >> Looks like you're using subranges with incremental repairs. This will >> generate a lot of anticompactions as you'll only repair a portion of the >> SSTables. You should use forceRepairAsync for incremental repairs so that >> it's possible for the repair to act on the whole SSTable, minimising >> anticompactions. >> >> Kurt Greaves >> k...@instaclustr.com >> www.instaclustr.com >> > -- > ----------------- > Alexander Dejanovski > France > @alexanderdeja > > Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com >
