[ https://issues.apache.org/jira/browse/CASSANDRA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vijay updated CASSANDRA-4858: ----------------------------- Attachment: 0001-CASSANDRA-4858.patch Simple and a hackie patch, We check if CL.One and RR is not true (FBU.threadLocalRandom().nextDouble()), then we will use this optimization. > Coverage analysis for low-CL queries > ------------------------------------ > > Key: CASSANDRA-4858 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4858 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Jonathan Ellis > Assignee: Vijay > Fix For: 1.2.1 > > Attachments: 0001-CASSANDRA-4858.patch > > > There are many cases where getRangeSlice creates more > RangeSliceCommand than it should, because it always creates one for each range > returned by getRestrictedRange. Especially for CL.ONE this does not take > the replication factor into account and is potentially pretty wasteful. > A range slice at CL.ONE on a 3 node cluster with RF=3 should only > ever create one RangeSliceCommand. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira