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 <dan...@kleviansky.com> wrote: > Hi everyone, > > Using The Last Pickle's fork of Reaper, and unfortunately running into a > bit of an issue. I'll try break it down below. > > # Problem Description: > * After starting repair via the GUI, progress remains at 0/x. > * Cassandra nodes calculate their respective token ranges, and then > nothing happens. > * There were no errors in the Reaper or Cassandra logs. Only a message of > acknowledgement that a repair had initiated. > * Performing stack trace on the running JVM, once can see that the thread > spawning the repair process was waiting on a lock that was never being > released. > * This occurred on all nodes, and prevented any manually initiated repair > process from running. A rolling restart of each node was required, after > which one could run a `nodetool repair` successfully. > > # Cassandra Cluster Details: > * Cassandra 2.2.5 running on Windows Server 2008 R2 > * 6 node cluster, split across 2 DCs, with RF = 3:3. > > # Reaper Details: > * Reaper 0.3.3 running on Windows Server 2008 R2, utilising a PostgreSQL > database. > > ## Reaper settings: > * Parallism: DC-Aware > * Repair Intensity: 0.9 > * Incremental: true > > Don't want to swamp you with more details or unnecessary logs, especially > as I'd have to sanitize them before sending them out, so please let me know > if there is anything else I can provide, and I'll do my best to get it to > you. > > Kind regards, > Daniel > -- ----------------- Alexander Dejanovski France @alexanderdeja Consultant Apache Cassandra Consulting http://www.thelastpickle.com