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

Michael Semb Wever commented on CASSANDRA-11928:
------------------------------------------------


Seems to be a regression in trunk of CASSANDRA-11465, the tracing doesn't use 
same consistency level as the request.
  trunk: 
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-dtest/856/testReport/junit/cql_tracing_test/TestCqlTracing/
  3.11: 
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-3.11-dtest/466/testReport/cql_tracing_test/TestCqlTracing/

My understanding is that tracing data was intended to be eventually consistent, 
and making it strictly consistency (via 
`-Dcassandra.wait_for_tracing_events_timeout_secs=xx`) was only for the purpose 
of testing. 

If that's true, a simple fix is just to reduce ccm nodes for that test, ie 
https://github.com/thelastpickle/cassandra-dtest/commit/f22f89fdb3080ac48f4310ee1a5aeb219ac2f093#diff-b866cba7cf982d53e6406cca014e659eR23

[~pauloricardomg], [~jkni], [~mambocab], thoughts? Is it worth bisecting where 
the regression came from? Or removing the 
`wait_for_tracing_events_timeout_secs` flag?

> dtest failure in cql_tracing_test.TestCqlTracing.tracing_simple_test
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-11928
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11928
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/dtest
>            Reporter: Craig Kodman
>            Priority: Normal
>              Labels: dtest, flaky
>
> example failure:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/727/testReport/cql_tracing_test/TestCqlTracing/tracing_simple_test
> Failed on CassCI build cassandra-3.0_dtest #727
> Is it a problem that the tracing message with the query is missing?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to