[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373537#comment-15373537
]
Jeremiah Jordan edited comment on CASSANDRA-9318 at 7/12/16 7:31 PM:
---------------------------------------------------------------------
[~jbellis] then we can default this to off.
I have interacted with *many* people using Cassandra that would actually like
to see some rate limiting applied for cases 1 and 2 such that things don't fall
over (shouldn't happen with new hints hopefully) or even hint like crazy.
Turning this on for them would allow that to happen.
was (Author: jjordan):
[~jbellis] then we can default this to off.
I have interacted with *many* people using Cassandra that would actually like
to see some rate limiting applied for cases 1 and 2 such that things don't fall
over (shouldn't happen with new hints hopefully) or even hint like crazy.
Turning this on would allow that to happen.
> 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)
