[ https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604740#comment-14604740 ]
Benedict commented on CASSANDRA-9318: ------------------------------------- bq. To be clear: all I'm effectively suggesting is we "hint" ... earlier. OK, so it looks like my understanding of hints was incorrect. However this statement is still valid, and still a better course of action. If we hint immediately, we buy ourselves breathing room _without affecting availability_. If this doesn't buy us enough breathing room, then blocking incoming writes is fine. But we should exhaust all our avenues that maintain our guarantees first, no? > 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)