nodes contain data for (prevTokenInRing, nodesOwnToken] (i.e. exclusive from previous token to inclusive of the nodes token). So .179 will contain things that hash in the range (152896308109140433971537345591636551711,0] and .12 will contain things that hash in range (0,152896308109140433971537345591636551711]. You can see this "visually" by noticing that .179 has 10% and .12 has 90% of the ring (~ 152896308109140433971537345591636551711 / 2^127).
On Mon, Feb 14, 2011 at 5:28 PM, mcasandra <mohitanch...@gmail.com> wrote: > > I installed cassandra and started it in multi-node. I set the InitialToken > to > 0. I ran nodetool and see: > > $ nodetool -h localhost ring > Address Status State Load Owns Token > > 152896308109140433971537345591636551711 > 172.16.20.179 Up Normal 7.52 KB 10.14% 0 > 172.16.20.12 Up Normal 12.5 KB 89.86% > 152896308109140433971537345591636551711 > > -- > Does it mean any keys between 0 - 152896308109140433971537345591636551711 > will go in Node 1 > and anything > 152896308109140433971537345591636551711 will go in Node 2? > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RandomPartitioner-tp6025203p6025659.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >
