Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 17 Aug 2016 03:53:21 +0000 (UTC)
From: "sankalp kohli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12512655.1309667529000.325478.1471406001067@Atlassian.JIRA>
In-Reply-To: <JIRA.12512655.1309667529000@Atlassian.JIRA>
References: <JIRA.12512655.1309667529000@Atlassian.JIRA> <JIRA.12512655.1309667529902@arcas>
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
archived-at: Wed, 17 Aug 2016 03:53:23 -0000


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

sankalp kohli commented on CASSANDRA-2848:
------------------------------------------

CASSANDRA-12256 is fixed now. Can we get this reviewed. 

> 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
>            Reporter: Chris Goffinet
>            Assignee: Geoffrey Yu
>            Priority: Minor
>             Fix For: 3.x
>
>         Attachments: 2848-trunk.txt
>
>
> 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.3.4#6332)