[CASSANDRA-14348] Per-request timeouts

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Component/s: Legacy/Coordination
• Assignee: Unassigned
• Reporter: Avi Kivity
• Created: 28/Mar/18 08:37
• Updated: 16/Apr/19 09:29
• Resolved: 28/Mar/18 09:01

Description

Cassandra currently allows separate timeout configuration for writes, single-partition reads, and range queries. However, this suffers from several deficiencies:

• configuration file changes must be replicated across all nodes, and the nodes must be restarted for them to take effect
• single-partition vs. large partition doesn't correlate with short vs. long queries, if you consider large partitions
• the same cluster may need to serve time-critical queries and non-critical queries simultaneously; there is no way to configure that.

We should have a way to configure the timeout at the request level, in the same way we can configure the consistency level. An alternative is to add a WITH TIMEOUT clause to CQL, similar to USING TTL or TIMESTAMP.

Issue Links

• duplicates: CASSANDRA-2848 Make the Client API support passing down timeouts