[ https://issues.apache.org/jira/browse/CASSANDRA-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460990#comment-16460990 ]
Stefan Podkowinski commented on CASSANDRA-14435: ------------------------------------------------ Quick way to give this a local test: * compile and start * jconsole localhost:7199 * Enable events if disabled in yaml: {{o.a.c.diag DiagnosticEventService}} -> {{resumePublishing()}} * Start emit dummy events: {{o.a.c.diag DummyEventEmitter}} -> {{dummyEventEmitIntervalMillis(1000)}} * Enable listening to dummy events: {{o.a.c.diag DiagnosticEvents}} -> {{enableEvents(org.apache.cassandra.diag.DummyEvent)}} * Go to {{o.a.c.diag DiagnosticEvents}} Notifications and subscribe > 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