Ah cool, I didn't realize reaper did that. On October 30, 2017 at 1:29:26 PM, Paulo Motta (pauloricard...@gmail.com) wrote:
> This is also the case for full repairs, if I'm not mistaken. Assuming I'm not > missing something here, that should mean that he shouldn't need to mark > sstables as unrepaired? That's right, but he mentioned that he is using reaper which uses subrange repair if I'm not mistaken, which doesn't do anti-compaction. So in that case he should probably mark data as unrepaired when no longer using incremental repair. 2017-10-31 3:52 GMT+11:00 Blake Eggleston <beggles...@apple.com>: >> Once you run incremental repair, your data is permanently marked as >> repaired > > This is also the case for full repairs, if I'm not mistaken. I'll admit I'm > not as familiar with the quirks of repair in 2.2, but prior to > 4.0/CASSANDRA-9143, any global repair ends with an anticompaction that marks > sstables as repaired. Looking at the RepairRunnable class, this does seem to > be the case. Assuming I'm not missing something here, that should mean that > he shouldn't need to mark sstables as unrepaired? --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
