[
https://issues.apache.org/jira/browse/CASSANDRA-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471772#comment-16471772
]
mck edited comment on CASSANDRA-14435 at 5/11/18 11:39 AM:
-----------------------------------------------------------
That or do like in CASSANDRA-13480 where there is an operation to check recent
events or something when notifications are lost. \{quote}
Yes, I think this is the idea [~cnlwsu]. With CASSANDRA-13460 it'll be possible
to query the list via a jmx endpoint (and a virtual table).
was (Author: michaelsembwever):
{quote}That or do like in CASSANDRA-13480 where there is an operation to check
recent events or something when notifications are lost. \{quote}
Yes, I think this is the idea [~cnlwsu]. With CASSANDRA-13460 it'll be possible
to query the list via a jmx endpoint (and a virtual table?).
> Diag. Events: JMX events
> ------------------------
>
> Key: CASSANDRA-14435
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14435
> Project: Cassandra
> Issue Type: New Feature
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
