cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9318) Bound the number of in-flight requests at the coordinator
Date Wed, 06 Jul 2016 00:33:11 GMT


Stefania commented on CASSANDRA-9318:

Thanks for your input [~jjordan]. I'm +1 with committing this to 3.0/3.9 disabled by default
as the impact should be minimal. For trunk, we can enable it by default provided we can test
it on a medium size cluster before committing. If that's not the case, we can commit it disabled
by default, and open a new follow-up ticket, to test it and enable it by default once it has
been tested.

We should probably also prepare a short paragraph for NEWS.txt [~sbtourist].

> Bound the number of in-flight requests at the coordinator
> ---------------------------------------------------------
>                 Key: CASSANDRA-9318
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local Write-Read Paths, Streaming and Messaging
>            Reporter: Ariel Weisberg
>            Assignee: Sergio Bossa
>         Attachments: 9318-3.0-nits-trailing-spaces.patch, backpressure.png, limit.btm,
> 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