[CASSANDRA-2848] Make the Client API support passing down timeouts

• Type: Improvement
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Fix Version/s: 4.0.x
• Component/s: Messaging/Client, Messaging/Internode
• Labels: protocolv5
• Complexity: Normal
• Impacts: Clients

Test and Documentation Plan

unit test and CI

• Assignee: Yifan Cai
• Reporter: Chris Goffinet

Authors

Yifan Cai

Reviewers

Dinesh Joshi, Jorge Bay

• Created: 03/Jul/11 04:32
• Updated: 10/Oct/20 00:05

Description

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.

Issue Links

• Blocked: CASSANDRA-15351 Allow configuring timeouts on the per-request basis
• is duplicated by: CASSANDRA-9205 Allow per statement time outs or request cancel method
• is duplicated by: CASSANDRA-14348 Per-request timeouts
• is related to: CASSANDRA-15499 Internode message builder does not add trace header
• is related to: CASSANDRA-5683 Nodetool command for modifying rpc_timeout
• is related to: CASSANDRA-9205 Allow per statement time outs or request cancel method
• relates to: CASSANDRA-2819 Split rpc timeout for read and write ops
• supercedes: CASSANDRA-5683 Nodetool command for modifying rpc_timeout