If you are using Murmur3 partitioner and do not wish to partake in vnodes you can still calculate inital_tokens. 

There is a guide here http://www.datastax.com/docs/1.2/initialize/token_generation#calculating-tokens-for-the-murmur3partitioner

Cheers
 
-----------------
Aaron Morton
Freelance Cassandra Developer
New Zealand

@aaronmorton

On 2/02/2013, at 9:59 AM, Edward Capriolo <edlinuxguru@gmail.com> wrote:

You do not just want to vnodes without being sure. Some queries are
not optimized for vnodes and issue 128 slices to solve some
secondaryIndexQueries.


On Fri, Feb 1, 2013 at 12:55 PM, Víctor Hugo Oliveira Molinar
<vhmolinar@gmail.com> wrote:
Do not set initial_token when using murmur3partitioner.
instead, set num_tokens.

For example, u have 3 hosts with the same hardware setup, then, for each one
set the same num_tokens.
But now consider adding another better host, this time i'd suggest you to
set previous num_tokens * 2.

num_tokens: 128 (worse machines)
num_tokens: 256(twice better machine)

This is the setup of virtual nodes.
Check current datastax docs for it.


On Thu, Jan 31, 2013 at 8:43 PM, Edward Capriolo <edlinuxguru@gmail.com>
wrote:

This is the bad side of changing default. There are going to be a few
groups unfortunates.

The first group, who only can not setup their cluster, and eventually
figure out their tokens. (this thread)
The second group, who assume their tokens were correct and run around
with an unbalanced cluster thinking the performance sucks. (the
threads for the next few months)
The third group, who will google "how to balance my ring" and find a
page with random partitioner instructions. (the occasional thread for
the next N years)
The fourth group, because as of now map reduce is highly confused by this.

On Thu, Jan 31, 2013 at 4:52 PM, Rob Coli <rcoli@palominodb.com> wrote:
On Thu, Jan 31, 2013 at 12:17 PM, Edward Capriolo
<edlinuxguru@gmail.com> wrote:
Now by default a new partitioner is chosen Murmer3.

"Now" = as of 1.2, to be unambiguous.

=Rob

--
=Robert Coli
AIM&GTALK - rcoli@palominodb.com
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb