[
https://issues.apache.org/jira/browse/CASSANDRA-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084584#comment-15084584
]
Yuki Morishita edited comment on CASSANDRA-8794 at 1/6/16 2:49 AM:
-------------------------------------------------------------------
Since 2.2, you can query {{system_distributed.parent_repair_history}} and
{{system_distributed.repair_history}} for on going repairs.
{{parent_repair_history}}'s record is created when repair is invoked, and
{{repair_hisotry}} entries are created and updated as repair progresses.
{{parent_repair_history}} is also updated when repair command finishes.
Closing as won't fix.
was (Author: yukim):
Since 2.2, you can query {{system_distributed.parent_repair_history}} and
{{system_distributed.repair_history}} for on going repairs.
{{parent_repair_history}}'s record is created when repair is invoked, and
{{repair_hisotry}} entries are created and updated as repair progresses.
{{parent_repair_history}} is also updated when repair command finishes.
> AntiEntropySessions doesn't show up until after a repair
> --------------------------------------------------------
>
> Key: CASSANDRA-8794
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8794
> Project: Cassandra
> Issue Type: Bug
> Components: Observability
> Reporter: Peter Halliday
> Assignee: Yuki Morishita
>
> The metric AntiEntropySessions for internal thread pools doesn't actually
> show up as an mbean until after a repair is run. This should actually be
> displayed before. This also, keeps any cluster that doesn't need repairing
> from displaying stats for AntiEntropySessions. The lack of the mbean's
> existence until after the repair will cause problem for various monitoring
> tools.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
