[ https://issues.apache.org/jira/browse/CASSANDRA-20202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-20202: ---------------------------------------- Fix Version/s: 4.1.x > 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.x > > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org