[
https://issues.apache.org/jira/browse/CASSANDRA-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111857#comment-16111857
]
Matt Byrd commented on CASSANDRA-8076:
--------------------------------------
Looks like this issue was trying to address a similar problem described in:
https://issues.apache.org/jira/browse/CASSANDRA-13480
In the patch there I added a method which allows one to get the parent repair
status of a given repair:
https://github.com/apache/cassandra/commit/20d5ce8b9b587be2f0b7bc5765254e8dc6e0bd3b
Which is sort of similar to the mentioned method here.
Additionally nodetool now also checks for this status when notifications are
lost and periodically so we don't hang indefinitely when notifications are lost.
Those using Jmx directly can do something analogous if the desire.
[~yukim] Would you mind taking a quick look CASSANDRA-13480 and If appropriate
close this as a duplicate of that?
> Expose an mbean method to poll for repair job status
> ----------------------------------------------------
>
> Key: CASSANDRA-8076
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8076
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Philip S Doctor
> Assignee: Yuki Morishita
> Attachments: 8076-2.0.txt
>
>
> Given the int reply-id from forceRepairAsync, allow a client to request the
> status of this ID via jmx.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
