cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9318) Bound the number of in-flight requests at the coordinator
Date Mon, 29 Jun 2015 16:09:05 GMT


Benedict commented on CASSANDRA-9318:

Do you mean within a single connection? I was under the impression we absolutely didn't want
to stop readers?

I disagree about not imposing _expectations_ on client implementations, so that users don't
need to reason about each connector they use independently. Along with the protocol spec,
other specs such as behaviour in these scenarios should really be spelled out. If clients
want to do their own thing, there's not much we can do, but it's helpful for users to have
an expectation of behaviour, and for implementors to be made aware of the potential problems
their driver may encounter that they do not anticipate (and what everyone will expect them
to do).

> Bound the number of in-flight requests at the coordinator
> ---------------------------------------------------------
>                 Key: CASSANDRA-9318
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message