[
https://issues.apache.org/jira/browse/CASSANDRA-17244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545698#comment-17545698
]
David Capwell commented on CASSANDRA-17244:
-------------------------------------------
with enough hacks was able to verify that its a timing bug... node1
(coordinator) works when the Read executor has task permits to allow running in
the current thread (isolated executor... coordinator blocks on local read), but
when it doesn't and needs to schedule it, it may see the error after the
coordinator already replied back to the user that the query failed... I have a
patch to do class rewriting so we block on node1 response...
> Fix
> org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition
> --------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17244
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17244
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> org.apache.cassandra.distributed.test.trackwarnings.TombstoneCountWarningTest.failThresholdSinglePartition
> failed
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1354/testReport/junit/org.apache.cassandra.distributed.test.trackwarnings/TombstoneCountWarningTest/failThresholdSinglePartition/]
> I didn't find any other occurrences but seems to me legit failure.
> CC [~dcapwell] as I think you were working on those and probably you will
> make better assessment than me. :)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
