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] Updated: (CASSANDRA-1198) In a cluster, get_range_slices() does not return all the keys it should
Date Sun, 20 Jun 2010 05:52:24 GMT

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

Jonathan Ellis updated CASSANDRA-1198:
--------------------------------------

    Attachment: 1198.txt

Excellent work.  Yes, the sort that was removed was in fact necessary (which is stated in
the docstring to getRestrictedRanges, but then the sort was done elsewhere so the confusion
was understandable).

This patch adds back the sort (this time in gRR) and moves the endpoints-handling to getRangeSlice
(where doing just-in-time liveness checking has the added benefit of improving availability
for large queries) to make gRR less muddled.

(Token-based range queries are turned into Bounds objects, which are start-inclusive, as opposed
to Range objects, which are not.)

> In a cluster, get_range_slices() does not return all the keys it should
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-1198
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1198
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7
>         Environment: Linux 2.6.18-128.1.10.el5.xs5.5.0.51xen
> Java build 1.6.0_17-b04
> Cassandra 0.7 2010-06-15 including patch for https://issues.apache.org/jira/browse/CASSANDRA-1130
>            Reporter: Christopher Gist
>            Assignee: Jeremy Hanna
>             Fix For: 0.7
>
>         Attachments: 1198.txt
>
>
> Row iteration with get_range_slices() does not return all keys. This behaviour only occurs
with more than one node and depends on how the nodes are located on the ring.
> To reproduce, insert some records into a cluster with more than one node. A subsequent
row iteration will return fewer records than were inserted. This has been observed when 1)
inserting into a single node, bootstrapping a second node then using get_range_slices() and
2) inserting into a cluster of several nodes then using get_range_slices().
> This appears to be similar to https://issues.apache.org/jira/browse/CASSANDRA-781

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message