search

thelastpickle / cassandra-reaper

Automated Repair Awesomeness for Apache Cassandra
http://cassandra-reaper.io/
Apache License 2.0
487 stars 217 forks source link

node null is locked by unknown/null for segment unknown #1236

Open JerryKwan opened 1 year ago

JerryKwan commented 1 year ago

Project board link

After running for a while, the log shows some like

DEBUG [2022-10-27 00:43:11,683] [xxxx:dbb73730-54fd-11ed-b33a-29eacc199335:dbb848bd-54fd-11ed-b33a-29eacc199335] i.c.s.CassandraStorage - node 104.225.xx.xx is locked by unknown/e8b68d00-55b6-11ed-b0ce-a3774c32f589 for segment unknown DEBUG [2022-10-27 00:43:11,683] [xxxx:dbb73730-54fd-11ed-b33a-29eacc199335:dbb848bd-54fd-11ed-b33a-29eacc199335] i.c.s.CassandraStorage - node null is locked by unknown/null for segment unknown DEBUG [2022-10-27 00:43:11,699] [xxxx:dbb73730-54fd-11ed-b33a-29eacc199335:dbb848bd-54fd-11ed-b33a-29eacc199335] i.c.s.CassandraStorage - Failed taking/renewing lock for repair dbb73730-54fd-11ed-b33a-29eacc199335 and segment dbb848bd-54fd-11ed-b33a-29eacc199335 because segments are already running for some nodes.

Why it prompts node null is locked y unknown/null for segment unknown? How can I fix it up?

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: REAP-84

adejanovski commented 1 year ago

Hi @JerryKwan,

do you still see this happening? Which version of Reaper are you running and what's your setup if it's the case (reaper config yaml, number of reaper instances, topology of your Cassandra cluster backing Reaper).