[ 
https://issues.apache.org/jira/browse/CASSANDRA-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-21831:
-------------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Open)

committed as 
https://github.com/apache/cassandra/commit/8b065275599bdcec401b9fdb1206c26a2cfba334

> Fix timeout flakiness in 
> PagingAggregationQueryTest.testAggregationWithRangeRowDeletionsComposite
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21831
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21831
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Test/unit
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 6.0, 6.0-alpha3, 7.0
>
>         Attachments: 
> ci_summary_thelastpickle_mck-CASSANDRA-21831-6.0_110.html, 
> results_details_thelastpickle_mck-CASSANDRA-21831-6.0_110.tar.xz
>
>
> {{testAggregationWithRangeRowDeletionsComposite}} became flaky with 
> CASSANDRA-11745.
> {noformat}
>   org.apache.cassandra.exceptions.ReadTimeoutException:
>   Operation timed out - received only 0 responses.
> {noformat}
>   The failure occurs during the full-range COUNT \(*), through 
> {{AggregationQueryPager.fetchNextRowIterator}}.
>   The fixture creates 100 partitions with 11 × 17 clustering combinations.  
> After range deletions, 14,300 rows remain. With a 1 KiB aggregation subpage 
> and 2,000-byte values, each subpage now holds only one row. Now, thousands of 
> subpage requests can exhaust the shared 10-second range-read deadline.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

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

Reply via email to