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
@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Upgrade from 1.1.10 to 1.2.4
Hello everybody,
I am trying to perform a rolling upgrade from 1.1.10 to 1.2.4 ( with two
patches to 1.2.4 https://issues.apache.org/jira/browse/CA
Hello everybody,
I am trying to perform a rolling upgrade from 1.1.10 to 1.2.4 ( with two
patches to 1.2.4 https://issues.apache.org/jira/browse/CASSANDRA-5554
https://issues.apache.org/jira/browse/CASSANDRA-5418 as they might effect us in
production )
I was wondering if anyone was able to
