cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-7807) Push notification when tracing completes for an operation
Date Fri, 27 Mar 2015 13:52:53 GMT


Robert Stupp updated CASSANDRA-7807:
    Attachment: 7807-v3.txt

I worked in all of your comments.

Regarding {{TransportException}} - unfortunately it’s an interface - not an (unchecked)
exception class.

I decided to check the version at the top-level methods (so removed the additional, paranoid
checks in the individual implementations)

Added functionality to {{Connection}}/{{ServerConnection}} that checks for registration.

removed that unnecessary stuff (so it doesn’t waste time)

Apologies for that.

> Push notification when tracing completes for an operation
> ---------------------------------------------------------
>                 Key: CASSANDRA-7807
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Robert Stupp
>            Priority: Minor
>              Labels: client-impacting, protocolv4
>             Fix For: 3.0
>         Attachments: 7807-v2.txt, 7807-v3.txt, 7807.txt
> Tracing is an asynchronous operation, and drivers currently poll to determine when the
trace is complete (in a loop with sleeps).  Instead, the server could push a notification
to the driver when the trace completes.
> I'm guessing that most of the work for this will be around pushing notifications to a
single connection instead of all connections that have registered listeners for a particular
event type.

This message was sent by Atlassian JIRA

View raw message