cassandra-commits mailing list archives

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


Ariel Weisberg commented on CASSANDRA-9318:

Benedict can you elaborate how 1 megabyte worth of mutations outstanding per node is blown
up into enough load or memory to bring down nodes? Is it that the multiplicative factor is
high, it's all routing to one place, or is it that the mutation stage acknowledges writes
as completed when the work hasn't been done and resources are still being tied up?

Maybe we have different definitions of in-flight. In my mind in-flight means that until the
response is sent back to the client the request counts against the in-flight limit.

> 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