Rana Aich <aichrana <at> gmail.com> writes: > > Yet my nodetool shows the following: > > 192.168.202.202Down 319.94 GB 7200044730783885730400843868815072654 |<--| > 192.168.202.4 Up 382.39 GB 23719654286404067863958492664769598669 | ^ > 192.168.202.2 Up 106.81 GB 36701505058375526444137310055285336988 v | > 192.168.202.3 Up 149.81 GB 65098486053779167479528707238121707074 | ^ > 192.168.202.201Up 154.72 GB 79420606800360567885560534277526521273 v | > 192.168.202.204Up 72.91 GB 85219217446418416293334453572116009608 | ^ > 192.168.202.1 Up 29.78 GB 87632302962564279114105239858760976120 v | > 192.168.202.203Up 9.35 GB 87790520647700936489181912967436646309 |-->|
It seems you did not configured tokens in your ring at all - automatic configuration is useless in practice. If you used random partitioning, for 8 nodes cluster these token configuration seems more reasonable: 1: 0 2: 21267647932558653966460912964485513216 3: 42535295865117307932921825928971026432 4: 63802943797675961899382738893456539648 5: 85070591730234615865843651857942052864 6: 106338239662793269832304564822427566080 7: 127605887595351923798765477786913079296 8: 148873535527910577765226390751398592512 You can generate token configuration for any cluster size by using tool http://people.apache.org/~pquerna/cassandra_tokens.py
