You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "mck (JIRA)" <ji...@apache.org> on 2018/05/17 21:55:00 UTC

[jira] [Commented] (CASSANDRA-14453) Improve visibility into repair state

    [ https://issues.apache.org/jira/browse/CASSANDRA-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479792#comment-16479792 ] 

mck commented on CASSANDRA-14453:
---------------------------------

Related to…
 - CASSANDRA-13480 – nodetool repair can hang forever if we lose the notification for the repair completing/failing
 which notifies the jmx client of missed events, and provides an jmx endpoint to fetch the repair state.
 I would really like to backport this to 3.11.x, as Reaper would take immediate benefit from it.
 - CASSANDRA-14435 – Diag. Events: JMX events
 which shifted focus on [~spodxx@gmail.com]'s work on Diagnostic Events to use jmx instead of something new, which the caveat of providing both notifications and a fetch endpoint, similar to CASSANDRA-13480

> Improve visibility into repair state
> ------------------------------------
>
>                 Key: CASSANDRA-14453
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14453
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Repair
>            Reporter: Blake Eggleston
>            Priority: Major
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org