[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604779#comment-14604779
]
Aleksey Yeschenko commented on CASSANDRA-9318:
----------------------------------------------
bq. Replica and coordinator are only identical on writes when RF=1, hardly the
most common case.
In non-toy clusters, with tons of clients, even at RF=1 they aren't, no
disagreement here. What I meant was that with the roles collocated on the same
machines (one request's replica is another node's coordinator), it's
insufficient to only handle protecting 'the coordinator' - an OOMd node is an
OOMd node. Eventually it has to be full-node.
> 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)
