[
https://issues.apache.org/jira/browse/CASSANDRA-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163296#comment-14163296
]
Mike Bulman edited comment on CASSANDRA-8076 at 10/8/14 10:20 AM:
------------------------------------------------------------------
This ticket is meant to stop the bleeding until CASSANDRA-5839 lands in 3.0.
We need a way to verify if a repair is actually still running, not necessarily
any details beyond that. Does c* keep it's active repair IDs in memory, and if
so can we simply expose the list of "current repair IDs" via JMX?
Amendment: pardon my potential ignorance here, but something like
ActiveRepairService.sessions seems like it would do the trick
was (Author: mbulman):
This ticket is meant to stop the bleeding until CASSANDRA-5839 lands in 3.0.
We need a way to verify if a repair is actually still running, not necessarily
any details beyond that. Does c* keep it's active repair IDs in memory, and if
so can we simply expose the list of "current repair IDs" via JMX?
> 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
>
> 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.3.4#6332)
