[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604697#comment-14604697
]
Jonathan Ellis commented on CASSANDRA-9318:
-------------------------------------------
# You can't just shed indiscriminately without breaking the contract that once
you've accepted a write (and not handed back UnavailableException) then you
must deliver it or hint it. You can't just drop it on the floor even to save
yourself from falling over. (If you fall over then at least it's clear to the
user that you weren't able to fulfill your contract. No, logging it isn't good
enough.)
# Again, shedding is strictly worse from a user's point of view than not
accepting a write we can't handle.
> 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.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)
