[
https://issues.apache.org/jira/browse/CASSANDRA-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461508#comment-16461508
]
Chris Lohfink commented on CASSANDRA-14435:
-------------------------------------------
Would be nice to be able to enable it for other mechanisms like native
transport but not JMX
While I think its a good idea here, we should probably at least have a note in
yaml about enabling it may impact operational tooling if using broadcaster.
With the shared event buffer (1000), the more we use it (even if no one is
listening to that mbean's events) the more lost notifications will occur. On an
active node we already end up losing a lot of events if the client is anywhere
with relevant latency from the node. Increasing the buffer isn't really a good
option as it puts massive pressure on the heap as the composite data objects
(particularly streaming ones) are huge.
> 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
