[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489629#comment-15489629
]
Sergio Bossa commented on CASSANDRA-9318:
-----------------------------------------
bq. queryStartNanoTime was introduced by CASSANDRA-12256
Yep, I was just looking at that.
bq. Should we increase the timeout by the amount of time spent waiting for the
backpressure strategy
Yes, this seems the best solution, plus documenting it, that is the fact that
with back-pressure enabled the time spent paused in back-pressure is not
counted against.
bq. Also, it should not be changed if the backpressure strategy is disabled.
I changed it regardless in the previous solution for consistency, but I agree
that post CASSANDRA-12256 it should be changed only in case of back-pressure.
> Bound the number of in-flight requests at the coordinator
> ---------------------------------------------------------
>
> Key: CASSANDRA-9318
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9318
> Project: Cassandra
> Issue Type: Improvement
> Components: Local Write-Read Paths, Streaming and Messaging
> Reporter: Ariel Weisberg
> Assignee: Sergio Bossa
> Attachments: 9318-3.0-nits-trailing-spaces.patch, backpressure.png,
> limit.btm, no_backpressure.png
>
>
> It's possible to somewhat bound the amount of load accepted into the cluster
> by bounding the number of in-flight requests and request bytes.
> An implementation might do something like track the number of outstanding
> bytes and requests and if it reaches a high watermark disable read on client
> connections until it goes back below some low watermark.
> Need to make sure that disabling read on the client connection won't
> introduce other issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
