Check that there are no running repair threads on the nodes with nodetool netstats.

For those that do have running repairs, restart C* on them to kill the repair threads and you should be able to repair the nodes again. Cheers!

On Wed, Nov 15, 2017 at 8:08 PM, Dipan Shah <dipan.sha@hotmail.com> wrote:

Hello,


I was running a "nodetool repair -pr" command on one node and due to some network issues I lost connection to the server.


Now when I am running the same command on that and other servers too, the repair job if failing with the following log:


[2017-11-15 03:55:19,965] Some repair failed
[2017-11-15 03:55:19,965] Repair command #1 finished in 0 seconds
error: Repair job has failed with the error message: [2017-11-15 03:55:19,965] Some repair failed
-- StackTrace --
java.lang.RuntimeException: Repair job has failed with the error message: [2017-11-15 03:55:19,965] Some repair failed
        at org.apache.cassandra.tools.RepairRunner.progress(RepairRunner.java:116)
        at org.apache.cassandra.utils.progress.jmx.JMXNotificationProgressListener.handleNotification(JMXNotificationProgressListener.java:77)
        at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.dispatchNotification(ClientNotifForwarder.java:583)
        at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.doRun(ClientNotifForwarder.java:533)
        at com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:452)
        at com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor$1.run(ClientNotifForwarder.java:108)

I found a few JIRA issues related to this but they were marked as fixed so I am not really sure if this is a bug. I am running Cassandra V 3.11.0.


One stackoverflow post suggested that I should restart all nodes and that seems to be overkill.


Can someone please guide me through this?


Thanks,

Dipan Shah