Yes. They were really just introduced and if you are ready to hitch your wagon to every new feature you put yourself in considerable risk. With any piece of software not just Cassandra.

On Fri, Jan 4, 2013 at 11:59 AM, Alain RODRIGUEZ <> wrote:
But I don't really get the point of starting a new cluster without vnodes... Is there some disadvantage using vnodes ?


2013/1/4 Nick Bailey <>
If you are planning on using murmur3 without vnodes (specifying your own tokens) there is a quick python script in the datastax docs you can use to generate balanced tokens.

On Fri, Jan 4, 2013 at 10:53 AM, Michael Kjellman <> wrote:
To be honest I haven't run a cluster with Murmur3.

You can still use indexing with RandomPartitioner (all us "old" folk are stuck on Random btw..)

And there was a thread floating around yesterday where Edward did some benchmarks and found that Murmur3 was actually slower than RandomPartitioner.

I do know that with vnodes token allocation is now 100% dynamic so no need to manually assign tokens to nodes anymore.


Date: Friday, January 4, 2013 8:48 AM
To: "''" <>
Subject: RE: Specifying initial token in 1.2 fails



Yes indeed – my mistake.  Thanks.  I can specify RandomPartitioner, since I do not use indexing – yet.


Just for informational purposes – with Murmur3 - to achieve a balanced cluster – is the initial token method supported?

If so – how should these be generated, the token-generator seems to only apply to RandomPartitioner.


Thanks again


From: Michael Kjellman []
Sent: Friday, January 04, 2013 8:39 AM
Subject: Re: Specifying initial token in 1.2 fails


Murmur3 != MD5 (RandomPartitioner)


From: Dwight Smith <>
Reply-To: "" <>
Date: Friday, January 4, 2013 8:36 AM
To: "''" <>
Subject: Specifying initial token in 1.2 fails




Just started evaluating 1.2 – starting a clean Cassandra node – the usual practice is to specify the initial token – but when I attempt to start the node the following is observed:


INFO [main] 2013-01-03 14:08:57,774 (line 203) disk_failure_policy is stop

DEBUG [main] 2013-01-03 14:08:57,774 (line 205) page_cache_hinting is false

INFO [main] 2013-01-03 14:08:57,774 (line 266) Global memtable threshold is enabled at 339MB

DEBUG [main] 2013-01-03 14:08:58,008 (line 381) setting auto_bootstrap to true

ERROR [main] 2013-01-03 14:08:58,024 (line 495) Fatal configuration error

org.apache.cassandra.exceptions.ConfigurationException: For input string: "85070591730234615865843651857942052863"

        at org.apache.cassandra.dht.Murmur3Partitioner$1.validate(

        at org.apache.cassandra.config.DatabaseDescriptor.loadYaml(

        at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(

        at org.apache.cassandra.service.CassandraDaemon.setup(

        at org.apache.cassandra.service.CassandraDaemon.activate(

        at org.apache.cassandra.service.CassandraDaemon.main(



This looks like a bug.






Join Barracuda Networks in the fight against hunger.
To learn how you can help in your community, please visit:


Join Barracuda Networks in the fight against hunger.
To learn how you can help in your community, please visit: