cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4858) Coverage analysis for low-CL queries
Date Fri, 18 Jan 2013 14:22:13 GMT


Sylvain Lebresne commented on CASSANDRA-4858:

You're right, we shouldn't merge if the right is the minimum token to avoid creating wrapping
ranges since CFS.getRangeSlice don't know what to do with them. Committed simple fix as 19972bdd91d6f8117eb8baa957b547000e995de3.
> Coverage analysis for low-CL queries
> ------------------------------------
>                 Key: CASSANDRA-4858
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2.1
>         Attachments: 0001-CASSANDRA-4858.patch, 0001-CASSANDRA-4858-v2.patch, 4858-cleanup.txt,
4858-v3-1.txt, 4858-v3-2.txt, 4858-v4.txt
> 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:

View raw message