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.
On Sun, Jun 23, 2013 at 2:31 AM, Ananth Gundabattula
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
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 anythin
