You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Podkowinski (JIRA)" <ji...@apache.org> on 2018/08/04 08:57:00 UTC
[jira] [Commented] (CASSANDRA-14435) Diag. Events: JMX events
[ https://issues.apache.org/jira/browse/CASSANDRA-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569129#comment-16569129 ]
Stefan Podkowinski commented on CASSANDRA-14435:
------------------------------------------------
The latest version of the code has been squashed and tested. It now basically follows the design as described in my previous post.
* [github|https://github.com/spodkowinski/cassandra/tree/CASSANDRA-14435]
* [circleci|https://circleci.com/gh/spodkowinski/cassandra/382]
* [dtests|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/602/]
> Diag. Events: JMX events
> ------------------------
>
> Key: CASSANDRA-14435
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14435
> Project: Cassandra
> Issue Type: New Feature
> Components: Observability
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Priority: Major
> Fix For: 4.x
>
>
> Nodes currently use JMX events for progress reporting on bootstrap and repairs. This might also be an option to expose diagnostic events to external subscribers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org