You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/07/11 18:18:05 UTC

[jira] [Assigned] (CASSANDRA-7535) Coverage analysis for range queries

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

Jonathan Ellis reassigned CASSANDRA-7535:
-----------------------------------------

    Assignee: Tyler Hobbs

> Coverage analysis for range queries
> -----------------------------------
>
>                 Key: CASSANDRA-7535
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7535
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: David Semeria
>            Assignee: Tyler Hobbs
>             Fix For: 2.0.9
>
>
> This is a regression related to https://issues.apache.org/jira/browse/CASSANDRA-4858
> Range queries are taking orders of magnitude more time to complete than before because the query planner is frequently unable to calculate the correct intersection of contiguous ranges for a given node.
> For example, SELECT * FROM TBL should result in exactly one scan at CL.ONE when RF = #nodes when in fact it can result in several hundred scans (sometimes thousands). The problem is exasperated with vnodes.
> The regression occurred at some point between 2.0.4 (which works fine) and 2.0.9.   



--
This message was sent by Atlassian JIRA
(v6.2#6252)