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

Sathyanarayanan Saravanamuthu commented on CASSANDRA-17217:
-----------------------------------------------------------

Hi [~yifanc] , one small query regarding the inflight read instructions. Let's 
say I make first read query to the cluster and the nodes 0 and 1 respond with 
failure and the client returns failure. The read to node 2 is in-flight; let's 
call this read as R1. Once the first call returns, I make second read query to 
the cluster. In the second query also nodes 0 and 1 respond with failure and 
the client returns failure. The read to node 2 is in-flight; let's call this 
read as R2. Does Cassandra assure that R1 is served first before R2?

> LocalReadSizeWarningTest#failThresholdSinglePartition is flaky
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-17217
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17217
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/unit
>            Reporter: Andres de la Peña
>            Assignee: Bernardo Botella Corbi
>            Priority: Normal
>             Fix For: 4.x
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The test 
> {{org.apache.cassandra.distributed.test.trackwarnings.LocalReadSizeWarningTest#failThresholdSinglePartition}}
>  seems to be flaky.
> It was discovered during CASSANDRA-17195 with [this CI 
> run|https://app.circleci.com/pipelines/github/adelapena/cassandra/1217/workflows/b366e352-0862-485a-acdc-5b75fe1ef575/jobs/11188].
> The failure can be reproduced running the test repeatedly for trunk, as it 
> can be seen 
> [here|https://app.circleci.com/pipelines/github/adelapena/cassandra/1219/workflows/a0c1fb7f-8a07-4fcf-97a4-7caf207dad78].



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to