[
https://issues.apache.org/jira/browse/CASSANDRA-7807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-7807:
------------------------------------
Attachment: 7807.txt
Attached patch adds:
* {{TRACING_FINISHED}} event - only payload is the trace-session-ID
* Event is only sent to those clients with the same {{InetAddress}} that
started the trace. I thought of limiting that to exactly that connection that
started the trace, but it would be too invasive and carry too much information
though the code (e.g. the {{Channel}} object - which might not be the channel
"containing" the control connection)
* Clients have to check the trace-session-ID in the event
* Event is sent when the last async mutation has finished and the
trace-session's status is {{STOPPED}}.
It may occur that trace information of nodes (other than the coordinator) is
not written when the trace-finished-event is sent. But that's exactly what can
happen when the {{system_traces.session}} table is polled.
> 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: 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)
