Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 22A1517DD6 for ; Fri, 8 May 2015 20:37:03 +0000 (UTC) Received: (qmail 28379 invoked by uid 500); 8 May 2015 20:37:03 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 28347 invoked by uid 500); 8 May 2015 20:37:03 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 28335 invoked by uid 99); 8 May 2015 20:37:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 May 2015 20:37:02 +0000 Date: Fri, 8 May 2015 20:37:02 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (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: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535449#comment-14535449 ] Jonathan Ellis edited comment on CASSANDRA-9318 at 5/8/15 8:36 PM: ------------------------------------------------------------------- bq. It currently bounds the number of in flight requests low enough Where? Are you talking about the hint limit? bq. I thought if we were capable of writing a hint we had to do it. The coordinator must write a hint *if a replica times out after it sends the mutation out.* (Because otherwise we leave the client wondering what state the cluster is left in; it might be on all replicas, or on none.) No hint is written for UnavailableException or OverloadedException, because we can guarantee the state -- it is on no replicas. was (Author: jbellis): bq. It currently bounds the number of in flight requests low enough Where? Are you talking about the hint limit? bq. I thought if we were capable of writing a hint we had to do it. We have to write a hint *if we send the mutation off to the replicas.* (Because otherwise we leave the client wondering what state the cluster is left in; it might be on all replicas, or on none.) No hint is written for UnavailableException or OverloadedException, because we can guarantee the state -- it is on no replicas. > 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 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)