[
https://issues.apache.org/jira/browse/CASSANDRA-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462629#comment-16462629
]
Chris Lohfink commented on CASSANDRA-14435:
-------------------------------------------
We should at least make it clear that there its just best effort and theres
high likelihood of missing events to make sure people dont rely on the events
for alerting or anything.
That or do like in CASSANDRA-13480 where there is an operation to check recent
events or something when notifications are lost. Can test with
{{-Djmx.remote.x.notification.buffer.size=1}}
> 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
