[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363288#comment-15363288
]
Jeremiah Jordan commented on CASSANDRA-9318:
--------------------------------------------
bq. One thing we did not confirm is whether you are happy committing this only
to trunk or whether you need this in 3.0. Strictly speaking 3.0 accepts only
bug fixes, not new features. However, this is an optional feature that solves a
problem (dropped mutations) and that is disabled by default, so we have a case
for an exception.
I think it would be nice for users to get this in 3.0/3.9 if you think it will
have minimal effect when disabled.
I also think it would be good to enable it by default in trunk. We have lots
of people who get put off by the fact that you can overload your cluster enough
to start dropping mutations, and the system doesn't "slow things down" such
that it can cope.
> 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)
