[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373696#comment-15373696
]
Jonathan Ellis commented on CASSANDRA-9318:
-------------------------------------------
bq. 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)
I think you just explained why that's not a very good reason to add more
complexity here, at least not without a demonstration that it's actually still
a problem.
bq. What if we tailored the algorithm to only: Rate limit if CL replicas are
below the high threshold / Throw exception if CL replicas are below the low
threshold.
But CL is per request. How do you disentangle that client side?
And we're still not solving what I think is (post file-based hints) the real
problem, my scenario 3. At this point instead of adding more complexity to an
approach that fundamentally doesn't solve that, why not back up and use an
approach that does the right thing in all 3 cases instead?
> 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)
