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

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

I completed the review of the latest commits and the code is in pretty good 
shape, we are almost ready to commit.

I still have the following points to clarify, concerning requirements, 
[~thobbs] can you give us your input since you have opened the ticket?
\\
* Is it OK to send the notification to the connection that originated the trace 
request even if it has not registered for the event (unlike other events). 
* Should other connections who have registered for this event receive 
notifications at all? From the description above it seems not but just to be 
extra sure.
* What should happen if the trace is started because of probabilistic tracing 
rather than a request from the client - should the client still receive the 
notification? What about sessions who registered (if applicable from previous 
point)? I believe this is what Robert was not sure about in his comment 
yesterday.

Regarding tests it's OK to defer to another ticket if the infrastructure is not 
available, thank you Ariel for your input.


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

Reply via email to