You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2016/01/06 03:49:40 UTC
[jira] [Resolved] (CASSANDRA-8794) AntiEntropySessions doesn't show
up until after a repair
[ https://issues.apache.org/jira/browse/CASSANDRA-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yuki Morishita resolved CASSANDRA-8794.
---------------------------------------
Resolution: Won't Fix
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)