Hello Rob, I ran into the stack trace when the situation was :
num_tokens unset ( by this I mean not specifying anything ) and initial_token set to some value. I was initially under the impression that specifying num_tokens will over ride the initial_token value and hence left num_tokens blank. I was able to get past that exception only when num_token was specified with a value of 1. Regards, Ananth On 6/25/13 3:27 AM, "Robert Coli" <rc...@eventbrite.com> wrote: >On Sun, Jun 23, 2013 at 2:31 AM, Ananth Gundabattula ><agundabatt...@threatmetrix.com> wrote: >> Looks like the cause of the error was because of not specifying >>num_tokens >> in the cassandra.yaml file. I was under the impression that setting a >>value >> of num_tokens will override the initial_token value . Looks like we >>need to >> set num_tokens to 1 to get around this error. Not specifying anything >>causes >> the above error. > >My understanding is that the 1.2.x behavior here is : > >1) initial_token set, num_tokens set = cassandra picks the num_tokens >value, ignores initial_token >2) initial_token unset, num_tokens unset = cassandra (until 2.0) picks >a single token via range bisection >3) initial_token unset, num_tokens set = cassandra uses num_tokens >number of vnodes > >Are you saying this is not the behavior you saw? > >=Rob
