Re: Cassandra 2.0 unbalanced ring with vnodes after adding new node

2014-06-09 Thread Владимир Рудев
Hmm, maybe, actually cluster was created not by me. Another interesting thing was yesterday - by some reason one old node lost one sstable file(no matter how - thats another problem) and we shut down this node, clean up all data, and start again. After this result of nodetool status K was this

Re: Cassandra 2.0 unbalanced ring with vnodes after adding new node

2014-06-09 Thread Jeremiah D Jordan
That looks like you started the initial nodes with num tokens=1, then later switched to vnodes, by setting num tokens to 256, then added that new node with 256 vnodes to start. Am I right? Since you don't have very much data, the easiest way out of this will be to decommission the original nod

Re: Cassandra 2.0 unbalanced ring with vnodes after adding new node

2014-06-05 Thread Marcelo Elias Del Valle
Actually, I have the same doubt. The same happens to me, but I guess it's because of lack of knowledge in Cassandra vnodes, somehow... I just added 3 nodes to my old 2 nodes cluster, now I have a 5 nodes cluster. As rows should be in a node calculated by HASH / number of nodes, adding a new node

Cassandra 2.0 unbalanced ring with vnodes after adding new node

2014-06-04 Thread Владимир Рудев
Hello to everyone! Please, can someone explain where we made a mistake? We have cluster with 4 nodes which uses vnodes(256 per node, default settings), snitch is default on every node: SimpleSnitch. These four nodes was from beginning of a cluster. In this cluster we have keyspace with this op