[ https://issues.apache.org/jira/browse/CASSANDRA-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461849#comment-16461849 ]
Chris Lohfink commented on CASSANDRA-14435: ------------------------------------------- Jmx notifications are stateless with clients. It keeps a cyclic buffer of events with ids. When a polling client sends for an update it sends last if seen. If the is is no longer in buffer the values between last read and lowest are lost. In between nvm and existing events going on that buffer we frequently lose events as is. Not that we can’t use it but it’s a global limited resource that can be sensitive with higher latenciea between jmx client and server > 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