High CPU after read timeout

Hi, Cassandra 3.9, I found after some ALLOW FILTERING request running on huge partition fails with Cassandra timeout during read query at consistency ONE (1 responses were required but only 0 replica responded) nodes continue to consume CPU in ReadStage-N threads, as if they still performing

Re: High CPU after read timeout

There is no mechanism for reads to timeout once they have started. The messaging service will drop the request when its received on the ReadStage or RequestResponseStage. This is how its always operated so not unique to 3.9. If a client disconnects from a coordinator there is also no way for the re

Re: High CPU after read timeout

> If a client disconnects from a coordinator there is also no way for the replicas to know that the client was disconnected. Got it. > Theres internal mechanisms that don't really have a concept of atimeout and where we would want it to never timeout Can such timeout be passed to executing t

Re: High CPU after read timeout

I've created JIRA https://issues.apache.org/jira/browse/CASSANDRA-13695 Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Fri, 14 Jul 2017 07:23:57 -0400 Vladimir Yudovin wrote > If a client disconnects from a coordinator ther