You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2015/07/09 19:28:04 UTC
[jira] [Created] (CASSANDRA-9772) Bound the number of concurrent
range requests
Tyler Hobbs created CASSANDRA-9772:
--------------------------------------
Summary: Bound the number of concurrent range requests
Key: CASSANDRA-9772
URL: https://issues.apache.org/jira/browse/CASSANDRA-9772
Project: Cassandra
Issue Type: Improvement
Components: Core
Reporter: Tyler Hobbs
Assignee: Tyler Hobbs
Fix For: 2.1.x, 2.2.x
After CASSANDRA-1337, we will execute requests for many token ranges concurrently based on our estimate of how many ranges will be required to meet the requested LIMIT. For queries with a lot of results this is generally fine, because it will only take a few ranges to satisfy the limit. However, for queries with very few results, this may result in the coordinator concurrently requesting all token ranges. On large vnode clusters, this will be particularly problematic.
Placing a simple bound on the number of concurrent requests is a good first step. Long-term, we should look into creating a new range command that supports requesting multiple ranges. This would eliminate the overhead of serializing and handling hundreds of separate commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)