[
https://issues.apache.org/jira/browse/CASSANDRA-11465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378934#comment-15378934
]
Stefania commented on CASSANDRA-11465:
--------------------------------------
So, the problem is not just the consistency level but also the fact that
{{TraceStateImpl.executeMutation()}} is completely asynchronous; I should have
read more carefully what [~thobbs] wrote above.
I have another version of the patch, in addition to reading at CL.ALL, we post
a no-op event to the TRACING stage before closing the tracing state. Because
the tracing executor only has one thread in its pool, this should guarantee
that the tracing mutations for this query have been applied to at least one
replica. I'm not sure if this is going to introduce slowness or deadlocks, and
we may have to put it behind a system flag to play it safe. Let's see what the
dtest results are first.
> 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)
