cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-9318) Bound the number of in-flight requests at the coordinator
Date Sun, 28 Jun 2015 16:32:05 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604763#comment-14604763
] 

Jonathan Ellis edited comment on CASSANDRA-9318 at 6/28/15 4:31 PM:
--------------------------------------------------------------------

Hinting is better than leaving things in an unknown state but it's not something we should
opt users into if we have a better option, since it basically turns the write into CL.ANY.

I think you're [Benedict] overselling how scary it is to stop reading new requests until we
can free up some memory from MS.  We're not dropping connections.  We're just imposing some
flow control.  Which is something that already happens at different levels anyway.


was (Author: jbellis):
Hinting is better than leaving things in an unknown state but it's not something we should
opt users into if we have a better option, since it basically turns the write into CL.ANY.

I think you're overselling how scary it is to stop reading new requests until we can free
up some memory from MS.  We're not dropping connections.  We're just imposing some flow control.
 Which is something that already happens at different levels anyway.

> Bound the number of in-flight requests at the coordinator
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-9318
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9318
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>             Fix For: 2.1.x, 2.2.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
issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message