[jira] [Commented] (CASSANDRA-2848) Make the Client API support passing down timeouts

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne commented on CASSANDRA-2848:
---------------------------------------------

I kind of maintain my objection that I don't think it's a good idea to expose this before we fix our timeout handling.

I doubt most user realize that the so-called "request timeout" are not always a reliable upper-bound on requests (and as said above, sometimes not even close), and we should imo fix that before exposing more fine-grained control, or we're just giving more rope for user to hang themselves. 

Note that fixing said timeout is not that hard, we should just do it first imo.

With that said, the patch modify both the native protocol and inter-node protocol, so I'm afraid it will have to wait on 4.0/native protocol v5.


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