cassandra-commits mailing list archives

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

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

Ariel Weisberg commented on CASSANDRA-7807:
-------------------------------------------

bq. SimpleClient only allows single threaded execution at the moment. But I’ve opened CASSANDRA-8728
for enhancements to native protocol testing. You can add that request (multi-threaded native
protocol testing) to this ticket? Although - i’m not sure whether we should do such special
(in the mean of a single ”flag”) kind of ”stress” testing in C* unit tests or whether
we shouldn’t all that testing hunting for races and such stuff to a special test suite to
also have process separation in place. IMO this is a separate discussion. (/cc Ariel Weisberg)

The only constraint I would add for unit tests (besides all the usual goodies like not being
fragile and passing consistently) is that they should run fast.

Trying to detect threading errors takes time and luck so it's not a good fit for a unit test.
Once we have that Jenkins job I am dreaming of we definitely have to add concurrent request
tracing as part of the load that it generates. Going to make a note of that.

> 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