>>> I do know that with vnodes token allocation is now 100% dynamic so no
>>> need to manually assign tokens to nodes anymore.
>>>
>>> Best,
>>> michael
>>>
>>> From: Dwight Smith
>>> Reply-To: "user@cassandr
nually assign tokens to nodes anymore.
>>
>> Best,
>> michael
>>
>> From: Dwight Smith
>> Reply-To: "user@cassandra.apache.org"
>> Date: Friday, January 4, 2013 8:48 AM
>> To: "'user@cassandra.apache.org'"
>> Su
ow 100% dynamic so no need
> to manually assign tokens to nodes anymore.
>
> Best,
> michael
>
> From: Dwight Smith
> Reply-To: "user@cassandra.apache.org"
> Date: Friday, January 4, 2013 8:48 AM
> To: "'user@cassandra.apache.org'"
>
l
From: Dwight Smith
mailto:dwight.sm...@genesyslab.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Friday, January 4, 2013 8:48 AM
To: "'user@cassandra.apache.org'"
mailto:user@cass
seems to only apply
to RandomPartitioner.
Thanks again
From: Michael Kjellman [mailto:mkjell...@barracuda.com]
Sent: Friday, January 04, 2013 8:39 AM
To: user@cassandra.apache.org
Subject: Re: Specifying initial token in 1.2 fails
Murmur3 != MD5 (RandomPartitioner)
From: Dwight Smith
er@cassandra.apache.org'"
mailto:user@cassandra.apache.org>>
Subject: Specifying initial token in 1.2 fails
Hi
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 follo
Hi
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 DatabaseDescriptor.java (line 203)
disk_failure_policy is stop
DEBUG [main
