On demand repairs with ERROR status #1307
Description
Description:
1- Does the problem persist?
Yes
2- Describe how to reproduce the issue:
- Deploy ecChronos with 2 datacenters with 3 Cassandra replicas each and 2 ecChronos, one for each datacenter.
- Create two tables tb1 and tb2 in the same keyspace.
- Restart ecchornos Pod from datacenter two.
- Trigger on-demand repair for the keyspace: "ecctool run-repairs -k ks --all" in both data centers.
- Check the repair status; some of them get an ERROR status in data center two.
Detailed description:
• What is happening?
On demand
repairs get ERROR status.
• What did you expect to happen?
repairs to work successfully.
• What have you tried?
• What version of ecChronos are you using?
Latest version of agent/master branch
• Was the problem detected during an upgrade or downgrade procedure?
No
• Have you checked the ecChronos documents?
Yes.
• What do YOU think is the issue?
There are Lock Acquisition Failures: Multiple "Unable to lock resource RepairResource-{node-id}-1" errors across both datacenter1 and datacenter2, but not sure if that is related to the ERROR.
• Anything else that is worth being noted?
Full logs will be shared with Victor.