cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2848) Make the Client API support passing down timeouts
Date Wed, 25 Jun 2014 07:10:24 GMT

    [ 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)

Mime
View raw message