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 3115F114A8 for ; Wed, 25 Jun 2014 07:10:25 +0000 (UTC) Received: (qmail 65121 invoked by uid 500); 25 Jun 2014 07:10:25 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 65089 invoked by uid 500); 25 Jun 2014 07:10:25 -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 65074 invoked by uid 99); 25 Jun 2014 07:10:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2014 07:10:24 +0000 Date: Wed, 25 Jun 2014 07:10:24 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-2848) Make the Client API support passing down timeouts 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-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043118#comment-14043118 ] Sylvain Lebresne commented on CASSANDRA-2848: --------------------------------------------- bq. The question is whether or not it's too late for it to make into native protocol v3 We have one remaining flag in the query/execute/batch options in the protocol, so it's easy to add without breaking the protocol v3 and so I don't think the protocol is necessarily a big problem in that instance (as in, we kind of could add it later). > Make the Client API support passing down timeouts > ------------------------------------------------- > > Key: CASSANDRA-2848 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2848 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Chris Goffinet > Priority: Minor > > Having a max server RPC timeout is good for worst case, but many applications that have middleware in front of Cassandra, might have higher timeout requirements. In a fail fast environment, if my application starting at say the front-end, only has 20ms to process a request, and it must connect to X services down the stack, by the time it hits Cassandra, we might only have 10ms. I propose we provide the ability to specify the timeout on each call we do optionally. -- This message was sent by Atlassian JIRA (v6.2#6252)