[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605817#comment-14605817
]
Jonathan Ellis edited comment on CASSANDRA-9318 at 6/29/15 4:10 PM:
--------------------------------------------------------------------
https://issues.apache.org/jira/browse/CASSANDRA-9318?focusedCommentId=14604775&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14604775
> [It is not] a good idea to try to allow extra reads when write capacity is
> full or vice versa. They both ultimately use the same resources (cpu, heap,
> disk i/o).
was (Author: jbellis):
https://issues.apache.org/jira/browse/CASSANDRA-9318?focusedCommentId=14604775&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14604775
> 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)
