[ 
https://issues.apache.org/jira/browse/CASSANDRA-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

C. Scott Andreas updated CASSANDRA-9772:
----------------------------------------
    Component/s: Coordination

> 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: Coordination
>            Reporter: Tyler Hobbs
>            Priority: Major
>             Fix For: 4.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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to