[ https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532938#comment-14532938 ]
Benedict commented on CASSANDRA-9318: ------------------------------------- bq. That will definitely be better than nothing Are you sure? To reiterate, we already bring down clusters with a stress write workload, despite a cap of < 1Mb on the in-flight coordinator-level write operations. We would be much better off imposing a simple bound on the number of items in the mutation stage, ala CASSANDRA-5039, since this would both be easier and likely more effective. > 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: 3.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)