[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489860#comment-15489860
]
Sergio Bossa commented on CASSANDRA-9318:
-----------------------------------------
[~slebresne], I do understand your concerns. I see [~Stefania] largely answered
them already, but it all depends on how strict we want to be in regards to
CASSANDRA-12256 and CASSANDRA-2848, so I propose one of the following:
1) We keep the timeout strict and change the back-pressure implementation to
wait at most the given timeout, and fail otherwise.
2) We add a back-pressure configuration parameter to have the users choose if
they want a strict timeout even in case of back-pressure, or they want it
"adaptive".
Thoughts?
> 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)
