Thanks, Eric and Peter, for all the replies ! It helped me a lot... I've read again the Getting Started page<http://www.datastax.com/docs/0.7/getting_started/index>... In fact I have particularly read the chapter : "setting up a multi node cluster" (as it was what I tried to do). It's written : "The rest of this section uses a two-node example cluster. With two nodes, a new Cassandra cluster’s load is automatically balanced, and remains balanced if you increase to four nodes, then eight". So I thought that keeping the default parameter (ie blank) would have been enough. So I think you should add in your doc (and in the yaml comments) that if it's the first node of your cluster, you really should set intialToken to 0, if you want your further nodes balanced.
You should add too, that if your cluster is unbalanced, you 'll have to run : nodetool host move newToken (it's not specified in this section). Some examples would be useful too. For people new to Cassandra, this part is very confusing (well, maybe I'm a little dumb too...) But even with these "flaws", your documentation is the best I have read. And if I have other issues, don't worry, you'll be informed :-). Thanks again, Patrick On Thu, Jan 20, 2011 at 8:55 PM, Eric Gilmore <e...@riptano.com> wrote: > Patrick, if you try adding capacity again from the beginning, I'd be > curious to hear if the > DataStax/Riptano<http://www.datastax.com/docs/0.7/operations/clustering#adding-capacity>docs > are helpful or not. > > Also, in the Getting Started > page<http://www.datastax.com/docs/0.7/getting_started/index>, > we note that it may be best to set initial_token to 0 on the very first node > that you start. > > Regards, > > Eric Gilmore > > > On Thu, Jan 20, 2011 at 11:05 AM, Peter Schuller < > peter.schul...@infidyne.com> wrote: > >> > Is it supposed to work that way, or have I missed something ? >> >> I don't see that you did anything wrong based on your description and >> based on my understanding how it works in 0.7 (not sure about 0.6), >> but hopefully someone else can address that part. What I can think of >> - did you inspect the log on the new node? Does it say anything about >> bootstraping or streaming data from other nodes? Does 'nodetool ring' >> indicate it considers itself completely up and in the cluster already? >> >> Trying to determine whether the node is in fact considering it self >> done bootstrapping and joined to the ring, yet containing no data. >> >> > I tried then to put values for initialToken for both nodes (stopping and >> > restartings the servers), but it didn't change anything : I have the >> same >> > token values... >> >> This is expected. Once the node has bootstrapped into the cluster and >> saved its token, it will no longer try to acquire a new one. Any >> initial token in the configuration is ignored; it is only the >> *initial* token, quite literally. Changing the token would require a >> 'nodetool move' command. >> >> -- >> / Peter Schuller >> > > > > -- > *Eric Gilmore > * > Consulting Technical Writer > Riptano, Inc. > Ph: 510 684 9786 (cell) > >
