cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7807) Push notification when tracing completes for an operation
Date Tue, 24 Mar 2015 13:56:53 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377894#comment-14377894
] 

Stefania commented on CASSANDRA-7807:
-------------------------------------

{{tracing_finished}} sounds better than {{trace_finished}} to me too. What I had in mind was
aligning with existing events,  which are a bit more generic, but that's OK if I am the only
one that feels this way we can keep {{tracing_finished}} and move on.

bq. I'm also not sure. Someone else?

{{QueryState.traceNextQuery()}} may return true even if the client has not activated tracing.
This happens randomly depending on the probability threshold set via {{nodetool settraceprobability}}.
Does this cover it?

I only had a quick look and I will resume tomorrow but if I understood correctly, the new
simple solution sends directly to the channel that made the request. So this event is nothing
like the existing client notifications, which are instead pushed to the control connection
provided the client has registered it with the event type?

> Push notification when tracing completes for an operation
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-7807
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7807
>             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
(v6.3.4#6332)

Mime
View raw message