cassandra-reaper icon indicating copy to clipboard operation
cassandra-reaper copied to clipboard

Repairs never start due to locks

Open kb-elmo opened this issue 4 years ago • 2 comments

It seems that Reaper is having some problem with the lock mechanism (race condition maybe?).

When trying to run a repair it never starts and the log just constantly shows

Cannot run segment <...> as another Reaper holds the lock on repair run <...>. Will try again later

This warning would make sense if there were any repair threads running but there aren't.

It seems that reaper is creating the locks without really creating the actual repair thread thus blocking itself.

Settings are DC-Aware full repair with 4 threads on a keyspace with one table.

┆Issue is synchronized with this Jira Task by Unito ┆Issue Number: K8SSAND-241

kb-elmo avatar Feb 06 '21 09:02 kb-elmo

I'd recommend to test the newly released 2.2.0 which has a brand new and more efficient locking system.

adejanovski avatar Feb 22 '21 16:02 adejanovski

@kb-elmo, are you still experiencing this issue with the latest versions of Reaper?

adejanovski avatar Mar 25 '22 09:03 adejanovski