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 Fri, 08 May 2015 22:25:04 GMT


Benedict commented on CASSANDRA-9318:

bq. Assuming we do this the way I am proposing  – after determining what replicas a mutation
belongs on

I may be being a bit dim, but I can't see a full proposal - [this comment|]
is the closest, and it doesn't mention this. Could you perhaps outline it for me explicitly,
so we're on the same page?

bq. Benedict can you remind me about what test your thinking of?

I meant the CASSANDRA-8789 follow up

> 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