cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9318) Bound the number of in-flight requests at the coordinator
Date Tue, 13 Sep 2016 13:40:21 GMT


Sergio Bossa commented on CASSANDRA-9318:

Testing should be now completed and all the main point have been verified:
1) No performance regressions with back-pressure disabled.
2) No performance regressions with back-pressure enabled and normally behaving cluster.
3) Reduced dropped mutations, typically by an order of magnitude, for continuous heavy write
workloads, and full recovery via hints: tested with a 4 nodes RF=3 cluster, ByteMan-based
rate limiting applied in several scenarios to one or more nodes, and "slow" back-pressure.

[~eduard.tudenhoefner], [~rhatch], do you have anything to add?

I've also fixed a bug along the way and rebased to the latest trunk: [~Stefania], do you mind
to have a final (hopefully!) review?

Updated patch and test runs:
| [trunk patch|]
| [testall|]
| [dtest|]
| [dtest (back-pressure enabled)|]

> 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