Re: Reaper repair seems to "hang"

2017-01-04 Thread Alexander Dejanovski
Actually, the problem is related to CASSANDRA-11430 . Before 2.2.6, the notification service did not work with newly deprecated repair methods, on which Reaper still currently relies. C* 2.2.6 and onwards are not affected by this problem and

Re: Reaper repair seems to "hang"

2017-01-03 Thread Bhuvan Rawal
Hi Daniel, Looks like yours is a different case. If you're running incremental repair for the first time it make take long time esp. if table is large. And repair may seem to stuck even when things are working. You can try nodetool compactionstats when repair appears stuck, you'll find a

Re: Reaper repair seems to "hang"

2017-01-03 Thread Daniel Kleviansky
Hi Bhuvan, Thank you so very much for your detailed reply. Just to ensure everyone is across the same information, and responses are not duplicated across two different forums, I thought I'd share with the mailing list that I've created a GitHub issue at:

Re: Reaper repair seems to "hang"

2017-01-03 Thread Bhuvan Rawal
Hi Daniel, We faced a similar issue during repair with reaper. We ran repair with more repair threads than number of cassandra nodes. But on and off repair was getting stuck and we had to do rolling restart of cluster or wait for lock time to expire (~1hr). We had a look at the stuck repair,

Re: Reaper repair seems to "hang"

2017-01-02 Thread Alexander Dejanovski
Hi Daniel, could you file a bug in the issue tracker ? https://github.com/thelastpickle/cassandra-reaper/issues We'll figure out what's wrong and get your repairs running. Thanks ! On Tue, Jan 3, 2017 at 12:35 AM Daniel Kleviansky wrote: > Hi everyone, > > Using The