You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2010/01/14 18:24:54 UTC
[jira] Resolved: (CASSANDRA-682) After bootstrap, some nodes cannot
find keys
[ https://issues.apache.org/jira/browse/CASSANDRA-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek resolved CASSANDRA-682.
-------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 0.9)
0.5
Same root cause as CASSANDRA-696.
> After bootstrap, some nodes cannot find keys
> --------------------------------------------
>
> Key: CASSANDRA-682
> URL: https://issues.apache.org/jira/browse/CASSANDRA-682
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.9
> Environment: debian lenny amd64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
> Reporter: Brandon Williams
> Fix For: 0.5
>
>
> I started a 3 node cluster with RF=3 and loaded about 3M keys into it. I proceeded to bootstrap a 4th node and it completed. Upon performing a read test, I found that two nodes could find all keys, and two nodes could find none, depending upon which machine I queried. Here is the ring output:
> Address Status Load Range Ring
> 127605887595351923798765477786913079296
> 10.242.4.13 Up 1023.44 MB 0 |<--|
> 10.242.4.10 Up 1.34 GB 42535295865117307932921825928971026432 | |
> 10.242.4.11 Up 1.33 GB 85070591730234615865843651857942052864 | |
> 10.242.4.12 Up 1.41 GB 127605887595351923798765477786913079296 |-->|
> Token 0 was the newly bootstrapped node. Tokens 127605887595351923798765477786913079296 and 85070591730234615865843651857942052864 were able to read all keys, the other two nodes were not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.