[
https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604746#comment-14604746
]
Benedict edited comment on CASSANDRA-9318 at 6/28/15 3:48 PM:
--------------------------------------------------------------
bq. This in no way affects our contract or guarantees, since we don't do
anything at all in the intervening period except consume memory.
bq. The whole point is that coordinators are falling over from OOM. This isn't
just something we can wave away as negligible.
I was referring here to the status quo, FTR.
Also FTR, we do clearly state hints are "best effort" (they also aren't
guaranteed to be persisted), so as far as contracts / guarantees are concerned,
I don't know we make any (and I wasn't aware of this one). It would be really
helpful for these (and many other) discussions if all of the assumptions,
contracts and guarantees we make about correctness and delivery were made
available in a single clearly spelled out document (and that, like the code
style, this document is the final arbiter of what action to take).
was (Author: benedict):
bq. This in no way affects our contract or guarantees, since we don't do
anything at all in the intervening period except consume memory.
bq. The whole point is that coordinators are falling over from OOM. This isn't
just something we can wave away as negligible.
I was referring here to the status quo, FTR.
Also FTR, we do clearly state hints are "best effort" (they also aren't
guaranteed to be persisted), so as far as contracts / guarantees are concerned,
I don't know we make any (and I wasn't aware of this one). It would be really
helpful for these (and many other) discussions if all of the assumptions,
contracts and guarantees we make about correctness and delivery were made
available in a single clearly spelled out document.
> 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)
