[jira] [Updated] (CASSANDRA-13459) Diag. Events: Native transport integration

["Stefan Podkowinski (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-13459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Podkowinski updated CASSANDRA-13459:
-------------------------------------------
    Attachment: diag.log

> Diag. Events: Native transport integration
> ------------------------------------------
>
>                 Key: CASSANDRA-13459
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13459
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: CQL
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>         Attachments: diag.log
>
>
> Events should be consumable by clients that would received subscribed events from the connected node. This functionality is designed to work on top of native transport with minor modifications to the protocol standard (see [original proposal|https://docs.google.com/document/d/1uEk7KYgxjNA0ybC9fOuegHTcK3Yi0hCQN5nTp5cNFyQ/edit?usp=sharing] for further considered options). First we have to add another value for existing event types. Also, we have to extend the protocol a bit to be able to specify a sub-class and sub-type value. E.g. {{DIAGNOSTIC_EVENT(GossiperEvent, MAJOR_STATE_CHANGE_HANDLED)}}. This still has to be worked out and I'd appreciate any feedback.
> There will also be a CLI tool shipped with Cassandra that enables users to dump events as JSON to stdout. This very simple tool will make use of a patched Python client driver that will work with the new {{DIAGNOSTIC_EVENT}} native transport event type.
> Invocation will simply look something like this {{./diagview event_class ..}}. See attached diag.log for example json output produced by starting and stopping another node.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)