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

Stefania commented on CASSANDRA-11465:
--------------------------------------

I found the reason of the sudden failures, it's [PR 
#1052|https://github.com/riptano/cassandra-dtest/pull/1052], specifically 
[here|https://github.com/riptano/cassandra-dtest/pull/1052/files#diff-b866cba7cf982d53e6406cca014e659eR75],
 merged on June 23. Previously we were just checking if "127.0.0.1", etc were 
present, now we check if "/127.0.0.1", etc are present. Note the forward slash. 
So my analysis above is correct, the only reason it did not fail before is 
because we were not testing it. 

I don't think we can easily fix the race in tracing, it's probably a known 
limitation, what we can do is query with a higher consistency level in cqlsh. 
Since [PYTHON-435|https://datastax-oss.atlassian.net/browse/PYTHON-435], 
released as part of driver version 3.3.0, the consistency level for trace 
queries can be set by the caller. I propose to use the same consistency level 
that is used for executing the statement in cqlsh, in this case it would be 
CL.ALL. However, we need to wait for CASSANDRA-11850 to upgrade the driver 
first.

[~JoshuaMcKenzie]: I don't think this is a show stopper for the release, we can 
either change the test back or leave the known failure, and once 11850 is 
available test this cqlsh patch 
[here|https://github.com/stef1927/cassandra/commit/8118c3dca34120b78f29a66c073208ee0de91063].

> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11465
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11465
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Stefania
>              Labels: dtest
>
> Failing on the following assert, on trunk only: 
> {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1087/testReport/cql_tracing_test/TestCqlTracing/tracing_unknown_impl_test
> Failed on CassCI build trunk_dtest #1087



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to