[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604790#comment-14604790
]
Aleksey Yeschenko commented on CASSANDRA-9318:
----------------------------------------------
bq. Yes. My point is that if we start by not accepting more than we can handle
coordinator-side we (a) improve things immediately by a nontrivial amount and
(b) we will have more clarity on what needs to be done replica-side.
Right. I'm all for flow control, in principle, and I'm not insisting on doing
it comprehensively in one ticket, or even one version. Sorry if I made it
non-clear. Not sure if it can be meaningfully done in 2.1, or that any of the
suggested options are workable - will reply later.
> 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
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Fix For: 2.1.x, 2.2.x
>
>
> 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)
