[ https://issues.apache.org/jira/browse/CASSANDRA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059243#comment-14059243 ]
Brandon Williams commented on CASSANDRA-7535: --------------------------------------------- By "2.0 head" I meant the latest 2.0 in the git repo, which is newer than 2.0.9, so I'm still not sure how to reproduce since that worked the same as 2.0.4 > 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.10 > > > This is a regression related to > [CASSANDRA-4858|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)