Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of staeff@gmail.com designates
 209.85.216.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:date:message-id:subject:from:to:content-type;
        b=pjDSdSO+AiBXDABZyf6OKMQfm2T0vCPDItao0MjO4XkDv+ACVzFhTn1+jJZf07QJx/
         z+bBsznh3gWaz01T0fSciDl1PNsWMEe8Z7neLLNavQBU2vZrqZVH/UrKEW6hWcoLNLY7
         06SF3CTCHroFbBooYuQ+hfHaEPASPeljGj6yI=
MIME-Version: 1.0
Reply-To: staeff@staeff.de
Date: Wed, 18 Aug 2010 09:52:29 +0000
Message-ID: <AANLkTimrRqBAd47g+YFu7vE0tSyrna+pTcKuB=oXrXHQ@mail.gmail.com>
Subject: uncomplete RangeSlices
From: Stefan Kaufmann <staeff@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=0016363104c5147ce4048e1606b8

--0016363104c5147ce4048e1606b8
Content-Type: text/plain; charset=ISO-8859-1

During my tests, I found some strange bootstrap + get Range Slice behavior.

In my testing environment im creating Datasets which look like those:
sampleDPUIDforTestingIssues1/00000000000
 -> value = 123456789
sampleDPUIDforTestingIssues1/00000999999
 -> value = 123456789

i create 1 Million of those Keys (increasing number at the end) and then I
have a query-script which uses get RangeSlices (10 000 Keys per Slices) in a
loop to query all keys. The script checks if all key's could be queried.

When I use the Bootstrap option to add a new node, mye query script shows me
a large amount of missing keys. (looks like the same key-range from one node
in the ring). However, when I try to query one single key out of the range
(not using slices), I can read the value without any problem.


My Script says:
Following errors for sampleDPUIDforTestingIssues1 collection found:
471886 - 736000 are missing.

This is the ring configuration:
Address       Status     Load
Range                                      Ring

sampleDPUIDforTestingIssues1/00000736000
10.20.10.112  Up         252.67 MB
qaDOmXnF48Q4sZks                                      |<--|
10.20.10.111  Up         252.67 MB
sampleDPUIDforTestingIssues1/00000471885   |   |
10.20.10.110  Up         252.66 MB
sampleDPUIDforTestingIssues1/00000736000   |-->|


When I add new nodes, by coping the storage/Keyspace data instead of
bootstrapping - everything works fine.

I searched the Issues-DB, and I found those two old ones..
(I'm not sure, if they really have to do something with this)

https://issues.apache.org/jira/browse/CASSANDRA-682
https://issues.apache.org/jira/browse/CASSANDRA-902

--0016363104c5147ce4048e1606b8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

During my tests, I found some strange bootstrap + get Range Slice behavior.=
<br><br>In my testing environment im creating Datasets which look like thos=
e:<br>sampleDPUIDforTestingIssues1/00000000000<br>=A0-&gt; value =3D 123456=
789<br>
sampleDPUIDforTestingIssues1/00000999999<br>=A0-&gt; value =3D 123456789<br=
><br>i create 1 Million of those Keys (increasing number at the end) and th=
en I have a query-script which uses get RangeSlices (10 000 Keys per Slices=
) in a loop to query all keys. The script checks if all key&#39;s could be =
queried. <br>
<br>When I use the Bootstrap option to add a new node, mye query script sho=
ws me a large amount of missing keys. (looks like the same key-range from o=
ne node in the ring). However, when I try to query one single key out of th=
e range (not using slices), I can read the value without any problem.<br>
<br><br>My Script says:<br>Following errors for sampleDPUIDforTestingIssues=
1 collection found: <br>471886 - 736000 are missing.<br><br>This is the rin=
g configuration:<br>Address=A0=A0=A0=A0=A0=A0 Status=A0=A0=A0=A0 Load=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 Range=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ring<br>


=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 sampleDPUIDforTestingIssues1/000007=
36000=A0=A0 <br>10.20.10.112=A0 Up=A0=A0=A0=A0=A0=A0=A0=A0 252.67 MB=A0=A0=
=A0=A0 qaDOmXnF48Q4sZks=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 =A0 =A0 =A0 =A0 =A0=A0=A0 |&lt;--|<br>10.20.10.111=
=A0 Up=A0=A0=A0=A0=A0=A0=A0=A0 252.67 MB=A0=A0=A0=A0 sampleDPUIDforTestingI=
ssues1/00000471885=A0=A0 |=A0=A0 |<br>


10.20.10.110=A0 Up=A0=A0=A0=A0=A0=A0=A0=A0 252.66 MB=A0=A0=A0=A0 sampleDPUI=
DforTestingIssues1/00000736000=A0=A0 |--&gt;|<br><br><br>When I add new nod=
es, by coping the storage/Keyspace data instead of bootstrapping - everythi=
ng works fine.<br><br>I searched the Issues-DB, and I found those two old o=
nes..<br>
(I&#39;m not sure, if they really have to do something with this)<br><br><a=
 href=3D"https://issues.apache.org/jira/browse/CASSANDRA-682">https://issue=
s.apache.org/jira/browse/CASSANDRA-682</a><br><a href=3D"https://issues.apa=
che.org/jira/browse/CASSANDRA-902">https://issues.apache.org/jira/browse/CA=
SSANDRA-902</a><br>


--0016363104c5147ce4048e1606b8--