Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates
 209.85.216.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CDECFCFA.11E95%agundabattula@threatmetrix.com>
References: <CDECA7E1.11E8B%agundabattula@threatmetrix.com>
	<CDECFCFA.11E95%agundabattula@threatmetrix.com>
Date: Mon, 24 Jun 2013 10:27:59 -0700
Message-ID: 
 <CAEDUwd1aTg2G+vp5BtegSV3X+osQTxc-KF7=FnzbaBuewTXx2g@mail.gmail.com>
Subject: Re: Upgrade from 1.1.10 to 1.2.4
From: Robert Coli <rcoli@eventbrite.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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