cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7807) Push notification when tracing completes for an operation
Date Tue, 24 Mar 2015 22:09:53 GMT


Benedict commented on CASSANDRA-7807:

bq. tracing_finished sounds better (to my german ears ... Benedict?).

Doesn't probably matter very much, and we seem to have an unclear use of language here as
it stands. From my POV, if only because I've been asked (so do ignore me), TRACE_FINISHED
makes more sense. That is assuming, as it appears, the event is unique to a single operation
on the cluster (i.e. one is emitted for a single successfully traced query). TRACING_FINISHED
implies the whole act of tracing has terminated (which may in fact still be ongoing for other
actions), whereas TRACE_FINISHED implies the one we're waiting for has. 

Grammatically, TRACE_COMPLETE is probably better though.

> 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.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