Skip to content
This repository has been archived by the owner on Mar 31, 2022. It is now read-only.

Terminating a repair through JMX will make Reaper consider the repair segment succeeded #98

Open
Yarin78 opened this issue Apr 30, 2015 · 0 comments
Open

Terminating a repair through JMX will make Reaper consider the repair segment succeeded #98

Yarin78 opened this issue Apr 30, 2015 · 0 comments

Comments

@Yarin78
Copy link
Contributor

Yarin78 commented Apr 30, 2015

This is not really Reapers fault, but rather a problem in Cassandra that doesn't report aborted repairs correctly. I've created a Cassandra ticket for this: https://issues.apache.org/jira/browse/CASSANDRA-9268

Note that this is only relevant for repairs that are aborted outside of Reaper. Repairs that are aborted by Reaper due to timeout are still handled correctly.
Bj0rnen added a commit that referenced this issue May 24, 2017
@Bj0rnen @adejanovski
Bump aborted runs down in cluster run summary (#98)
11eabea 
Null fields put old aborted runs high in the sort order for repair
runs history of a cluster. This moves those down to an appropriate
position.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Yarin78