cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9772) Bound the number of concurrent range requests
Date Fri, 22 Jul 2016 17:04:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389834#comment-15389834
] 

Jonathan Ellis commented on CASSANDRA-9772:
-------------------------------------------

Is this a problem for SASI [~beobal] [~xedin]?

> Bound the number of concurrent range requests
> ---------------------------------------------
>
>                 Key: CASSANDRA-9772
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9772
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Tyler Hobbs
>             Fix For: 3.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)

Mime
View raw message