I have 3 nodes A, B, C with RF=3. When I configure the cluster and before start taking any read/write request, I first start A, put A itself as seed (following in the instructions on wiki), and then start B (put A as the seed) and then start C (also put A as the seed).
B and C seem joining the ring correctly and the cluster is working properly but if I run nodetool cla...@a:$ nodetool -h A -p 9090 ring Address Status Load Range Ring 170141183460469231731687303715884105726 192.168.11.29 Up 2.29 GB 56713727820156410577229101238628035242 |<--| 192.168.11.28 Up 2.18 GB 113427455640312821154458202477256070484 | | 192.168.11.27 Up 2.29 GB 170141183460469231731687303715884105726 |-->| cla...@a:$ nodetool -h B -p 9090 ring Address Status Load Range Ring 170141183460469231731687303715884105726 192.168.11.29 Down 2.28 GB 56713727820156410577229101238628035242 |<--| 192.168.11.28 Up 2.18 GB 113427455640312821154458202477256070484 | | 192.168.11.27 Down 2.28 GB 170141183460469231731687303715884105726 |-->| cla...@a:$ nodetool -h C -p 9090 ring Address Status Load Range Ring 170141183460469231731687303715884105726 192.168.11.29 Up 2.29 GB 56713727820156410577229101238628035242 |<--| 192.168.11.28 Down 2.18 GB 113427455640312821154458202477256070484 | | 192.168.11.27 Up 2.29 GB 170141183460469231731687303715884105726 |-->| Any reason why nodetool thinks that some servers are down if pointing to B or C? If my cluster setup correct? thanks, Claire