cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12944) Diagnostic Events
Date Wed, 22 Mar 2017 15:20:41 GMT


Stefan Podkowinski commented on CASSANDRA-12944:

My first version of the unit testing side of this tickets is now mostly completed. I've added
to illustrate how events can be collected during a test and afterwards inspected if they match
what you'd expect to happen.

In short diagnostic events will improve unit testing by a) providing test flow control instances
between events in form of CompletableFutures (see [|])
and b) validate state and behavior by allowing you to inspect generated events (see mentioned
Minor API changes will likely still happen, but that will be mostly it, if you don't have
any more feedback.

At some point I'm also going to break up this ticket into easier to review subtasks for
* core classes (pub/sub, base event classes, number of event implementations)
* unit testing classes (including examples and docs)
* native transport integration (maybe with CLI prototype that would dump events to console)

> Diagnostic Events
> -----------------
>                 Key: CASSANDRA-12944
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: Stefan Podkowinski
> I'd like to propose a new "diagnostic events" feature that would allow to observe internal
Cassandra events in unit tests and from external tools via native transport. The motivation
is to improve testing as well as operational monitoring and troubleshooting beyond logs and
> Please find more details in the linked proposal and give it some thoughts :)

This message was sent by Atlassian JIRA

View raw message