After running some tests I can confirm that using -pr leaves unrepaired SSTables, while removing it shows repaired SSTables only once repair is completed.
The purpose of -pr was to lighten the repair process by not repairing ranges RF times, but just once. With incremental repair though, repaired data is marked as such and will be skipped on the next session, making -pr kinda useless. I must admit that I fail to understand currently how running repair with -pr could leave unrepaired data though, even when ran on all nodes in all DCs, and how that could be specific to incremental repair (and would appreciate if someone shared the explanation). On a side note, I have a Spotify Reaper fork that handles incremental repair, and embeds the UI of Stefan Podkowinski, tweaked to add incremental repair inputs : https://github.com/adejanovski/cassandra-reaper/tree/inc-repair-support-with-ui Compile it with maven and run with : java -jar target/cassandra-reaper-0.2.4-SNAPSHOT.jar server resource/cassandra-reaper.yaml Then go to http://127.0.0.1:8081/webui/ Le ven. 26 août 2016 à 12:58, Stefano Ortolani <ostef...@gmail.com> a écrit : > Hi Paulo, could you elaborate on 2? > I didn't know incremental repairs were not compatible with -pr > What is the underlying reason? > > Regards, > Stefano > > > On Fri, Aug 26, 2016 at 1:25 AM, Paulo Motta <pauloricard...@gmail.com> > wrote: > >> 1. Migration procedure is no longer necessary after CASSANDRA-8004, and >> since you never ran repair before this would not make any difference >> anyway, so just run repair and by default (CASSANDRA-7250) this will >> already be incremental. >> 2. Incremental repair is not supported with -pr, -local or -st/-et >> options, so you should run incremental repair in all nodes in all DCs >> sequentially (you should be aware that this will probably generate inter-DC >> traffic), no need to disable autocompaction or stopping nodes. >> >> 2016-08-25 18:27 GMT-03:00 Aleksandr Ivanov <ale...@gmail.com>: >> >>> I’m new in Cassandra and trying to figure out how to _start_ using >>> incremental repairs. I have seen article about “Migrating to incremental >>> repairs” but since I didn’t use repairs before at all and I use Cassandra >>> version v3.0.8, then maybe not all steps are needed which are mentioned in >>> Datastax article. >>> Should I start with full repair or I can start with executing “nodetool >>> repair -pr my_keyspace” on all nodes without autocompaction disabling and >>> node stopping? >>> >>> I have 6 datacenters with 6 nodes in each DC. Is it enough to run >>> “nodetool repair -pr my_keyspace” in one DC only or it should be executed >>> on all nodes in _all_ DCs? >>> >>> I have tried to perform “nodetool repair -pr my_keyspace” on all nodes >>> in all datacenters sequentially but I still can see non repaired SSTables >>> for my_keyspace (Repaired at: 0). Is it expected behavior if during >>> repair data in my_keyspace wasn’t modified (no writes, no reads)? >>> >> >> >
