You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2018/03/28 09:08:00 UTC
[jira] [Commented] (CASSANDRA-14348) Per-request timeouts
[ https://issues.apache.org/jira/browse/CASSANDRA-14348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417070#comment-16417070 ]
Sylvain Lebresne commented on CASSANDRA-14348:
----------------------------------------------
This is a duplicate of CASSANDRA-2848 and I encourage to keep the discussion there. The short status though is that as far as I can tell, it's not controversial that this would be a good thing, but our existing code around timeout handling makes this a bit harder to do correctly that one would hope and while there has been some work on it, the cycles to do this right haven't been fully put into it yet. Obviously, help always appreciated.
> 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
> Priority: Major
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org