[CASSANDRA-682] After bootstrap, some nodes cannot find keys

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Fix Version/s: 0.5

Environment

debian lenny amd64 OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)

• Severity: Normal
• Assignee: Unassigned
• Reporter: Brandon Williams
• Created: 07/Jan/10 17:49
• Updated: 16/Apr/19 09:33
• Resolved: 14/Jan/10 17:24

Description

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.

Issue Links

• is part of: CASSANDRA-696 Bootstrapping doesn't work on new clusters