Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 8 May 2015 22:25:04 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12827721.1430931031000.58958.1431123904576@Atlassian.JIRA>
In-Reply-To: <JIRA.12827721.1430931031000@Atlassian.JIRA>
References: <JIRA.12827721.1430931031000@Atlassian.JIRA>
 <JIRA.12827721.1430931031849@arcas>
Subject: [jira] [Commented] (CASSANDRA-9318) Bound the number of in-flight
 requests at the coordinator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-9318?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
14535755#comment-14535755 ]=20

Benedict commented on CASSANDRA-9318:
-------------------------------------

bq. Assuming we do this the way I am proposing  =E2=80=93 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|h=
ttps://issues.apache.org/jira/browse/CASSANDRA-9318?focusedCommentId=3D1453=
5356&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpane=
l#comment-14535356] 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: https://issues.apache.org/jira/browse/CASSANDRA-9318
>             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 clus=
ter 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 clie=
nt connections until it goes back below some low watermark.
> Need to make sure that disabling read on the client connection won't intr=
oduce other issues.


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