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

Michael Semb Wever updated CASSANDRA-20202:
-------------------------------------------
          Fix Version/s: 4.1.9
                         5.0.4
                         5.1
                             (was: 5.x)
                             (was: 4.1.x)
                             (was: 5.0.x)
          Since Version: 4.1.8
    Source Control Link: 
https://github.com/apache/cassandra/commit/291cbcccf6e472b455a9d3ef2602b68ae0b7797c
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

Committed as 
https://github.com/apache/cassandra/commit/291cbcccf6e472b455a9d3ef2602b68ae0b7797c

> Test failure: org.apache.cassandra.transport.SimpleClientPerfTest
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-20202
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20202
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Messaging/Client, Test/burn
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 4.1.9, 5.0.4, 5.1
>
>         Attachments: ci_summary_thelastpickle_mck-samt-20202-5.0_163.html, 
> client_capacity_after.png, client_capacity_leak_before.png, 
> lack_of_client_capacity_moment.png, 
> results_details_thelastpickle_mck-samt-20202-5.0_163.tar.xz
>
>
> SimpleClient uses a CQLMessageHandler instance to deal with response messages 
> in the V5 framing format. It looks like CASSANDRA-16663 broke SimpleClient's 
> ability to return capacity allocated during the processing of inbound 
> messages (i.e. responses from server->client) back to the global and 
> per-endpoint resource monitors. The change in behaviour introduced in 
> CASSANDRA-20052, in which we now push back to the client when a capacity for 
> a large message can't be allocated, causes SimpleClientPerfTest in the burn 
> suite to fail on V5/V6. This is purely because the test expects the client to 
> run for a fixed period without interruption, but now it halts as soon as 
> capacity is exhausted. The simple fix is to restore SimpleClient's capacity 
> return.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to