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

mck commented on CASSANDRA-14452:
---------------------------------

Related to CASSANDRA-13480 and CASSANDRA-14435, see this comment.

> Improve JMX interface for repair
> --------------------------------
>
>                 Key: CASSANDRA-14452
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14452
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Repair
>            Reporter: Blake Eggleston
>            Priority: Major
>
> The jmx interface for repair is a weak point, operationally. Nodetool relies 
> on an unbroken connection, and jmx notifications to communicate 
> progress/success/failure to the caller.  This causes all sorts of problems 
> with regard to determining the actual state of a repair. This should be 
> reworked so nodetool can just poll the coordinator for the state of a repair 
> with an id, and can therefore handle dropped messages and broken jmx 
> connections.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to