cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Holmberg (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2848) Make the Client API support passing down timeouts
Date Tue, 24 Apr 2018 14:12:01 GMT


Adam Holmberg updated CASSANDRA-2848:
    Labels: client-impacting  (was: )

> Make the Client API support passing down timeouts
> -------------------------------------------------
>                 Key: CASSANDRA-2848
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Chris Goffinet
>            Assignee: Dinesh Joshi
>            Priority: Minor
>              Labels: client-impacting
>             Fix For: 3.11.x
>         Attachments: 2848-trunk-v2.txt, 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message