cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9318) Bound the number of in-flight requests at the coordinator
Date Fri, 08 May 2015 20:36:01 GMT


Jonathan Ellis commented on CASSANDRA-9318:

bq. It currently bounds the number of in flight requests low enough

Where?  Are you talking about the hint limit?

bq. I thought if we were capable of writing a hint we had to do it. 

We have to write a hint *if we send the mutation off to the replicas.*  (Because otherwise
we leave the client wondering what state the cluster is left in; it might be on all replicas,
or on none.)  No hint is written for UnavailableException or OverloadedException, because
we can guarantee the state -- it is on no replicas.

> 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
> 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