[
https://issues.apache.org/jira/browse/CASSANDRA-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-14453:
------------------------------------
Reviewers: Paulo Motta
> Improve visibility into repair state
> ------------------------------------
>
> Key: CASSANDRA-14453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14453
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: Blake Eggleston
> Priority: Normal
> Labels: gsoc2021, mentor
>
> Most of the repair flow is fire and forget, where we send a message, or start
> a job with a remote component, and then wait for a response of some type, or
> for the failure detector to tell us a node has died. This leaves several
> cases where the repair can hang, and operators have to guess about it’s
> state, and the best course of action. It would help if the state of a given
> repair could be polled, and possibly cancelled. This is going to involve
> touching the validation, anti-compaction, and streaming code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
