Avi Kivity created CASSANDRA-14348:
--------------------------------------
Summary: Per-request timeouts
Key: CASSANDRA-14348
URL: https://issues.apache.org/jira/browse/CASSANDRA-14348
Project: Cassandra
Issue Type: Improvement
Components: Coordination
Reporter: Avi Kivity
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
