You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Dwight Smith <Dw...@genesyslab.com> on 2013/01/04 17:36:31 UTC
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 following is observed:
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 203) disk_failure_policy is stop
DEBUG [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 205) page_cache_hinting is false
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 266) Global memtable threshold is enabled at 339MB
DEBUG [main] 2013-01-03 14:08:58,008 DatabaseDescriptor.java (line 381) setting auto_bootstrap to true
ERROR [main] 2013-01-03 14:08:58,024 DatabaseDescriptor.java (line 495) Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: For input string: "85070591730234615865843651857942052863"
at org.apache.cassandra.dht.Murmur3Partitioner$1.validate(Murmur3Partitioner.java:180)
at org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:433)
at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:121)
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:178)
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:397)
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440)
This looks like a bug.
Thanks
Re: Specifying initial token in 1.2 fails
Posted by Edward Capriolo <ed...@gmail.com>.
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 <ar...@gmail.com> wrote:
> But I don't really get the point of starting a new cluster without
> vnodes... Is there some disadvantage using vnodes ?
>
> Alain
>
>
> 2013/1/4 Nick Bailey <ni...@datastax.com>
>
>> 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.
>>
>>
>> http://www.datastax.com/docs/1.2/initialize/token_generation#calculating-tokens-for-the-murmur3partitioner
>>
>>
>> On Fri, Jan 4, 2013 at 10:53 AM, Michael Kjellman <
>> mkjellman@barracuda.com> 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.
>>>
>>> http://www.mail-archive.com/user@cassandra.apache.org/msg26789.html<http://permalink.gmane.org/gmane.comp.db.cassandra.user/30182>
>>>
>>> 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 <Dw...@genesyslab.com>
>>> Reply-To: "user@cassandra.apache.org" <us...@cassandra.apache.org>
>>> Date: Friday, January 4, 2013 8:48 AM
>>> To: "'user@cassandra.apache.org'" <us...@cassandra.apache.org>
>>> Subject: RE: Specifying initial token in 1.2 fails
>>>
>>> Michael****
>>>
>>> ** **
>>>
>>> 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 [mailto:mkjellman@barracuda.com<mk...@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 <Dw...@genesyslab.com>
>>> *Reply-To: *"user@cassandra.apache.org" <us...@cassandra.apache.org>
>>> *Date: *Friday, January 4, 2013 8:36 AM
>>> *To: *"'user@cassandra.apache.org'" <us...@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 following is observed:****
>>>
>>> ****
>>>
>>> INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 203)
>>> disk_failure_policy is stop****
>>>
>>> DEBUG [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 205)
>>> page_cache_hinting is false****
>>>
>>> INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 266)
>>> Global memtable threshold is enabled at 339MB****
>>>
>>> DEBUG [main] 2013-01-03 14:08:58,008 DatabaseDescriptor.java (line 381)
>>> setting auto_bootstrap to true****
>>>
>>> ERROR [main] 2013-01-03 14:08:58,024 DatabaseDescriptor.java (line 495)
>>> Fatal configuration error****
>>>
>>> org.apache.cassandra.exceptions.ConfigurationException: For input
>>> string: "85070591730234615865843651857942052863"****
>>>
>>> at
>>> org.apache.cassandra.dht.Murmur3Partitioner$1.validate(Murmur3Partitioner.java:180)
>>> ****
>>>
>>> at
>>> org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:433)
>>> ****
>>>
>>> at
>>> org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:121)
>>> ****
>>>
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:178)
>>> ****
>>>
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:397)
>>> ****
>>>
>>> at
>>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440)
>>> ****
>>>
>>> ****
>>>
>>> ****
>>>
>>> This looks like a bug.****
>>>
>>> ****
>>>
>>> Thanks****
>>>
>>> ****
>>>
>>> ****
>>>
>>> ** **
>>>
>>> ----------------------------------
>>> Join Barracuda Networks in the fight against hunger.
>>> To learn how you can help in your community, please visit:
>>> http://on.fb.me/UAdL4f ****
>>>
>>> ****
>>>
>>> ----------------------------------
>>> Join Barracuda Networks in the fight against hunger.
>>> To learn how you can help in your community, please visit:
>>> http://on.fb.me/UAdL4f
>>>
>>>
>>
>>
>
Re: Specifying initial token in 1.2 fails
Posted by Alain RODRIGUEZ <ar...@gmail.com>.
But I don't really get the point of starting a new cluster without
vnodes... Is there some disadvantage using vnodes ?
Alain
2013/1/4 Nick Bailey <ni...@datastax.com>
> 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.
>
>
> http://www.datastax.com/docs/1.2/initialize/token_generation#calculating-tokens-for-the-murmur3partitioner
>
>
> On Fri, Jan 4, 2013 at 10:53 AM, Michael Kjellman <mkjellman@barracuda.com
> > 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.
>>
>> http://www.mail-archive.com/user@cassandra.apache.org/msg26789.html<http://permalink.gmane.org/gmane.comp.db.cassandra.user/30182>
>>
>> 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 <Dw...@genesyslab.com>
>> Reply-To: "user@cassandra.apache.org" <us...@cassandra.apache.org>
>> Date: Friday, January 4, 2013 8:48 AM
>> To: "'user@cassandra.apache.org'" <us...@cassandra.apache.org>
>> Subject: RE: Specifying initial token in 1.2 fails
>>
>> Michael****
>>
>> ** **
>>
>> 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 [mailto:mkjellman@barracuda.com<mk...@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 <Dw...@genesyslab.com>
>> *Reply-To: *"user@cassandra.apache.org" <us...@cassandra.apache.org>
>> *Date: *Friday, January 4, 2013 8:36 AM
>> *To: *"'user@cassandra.apache.org'" <us...@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 following is observed:****
>>
>> ****
>>
>> INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 203)
>> disk_failure_policy is stop****
>>
>> DEBUG [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 205)
>> page_cache_hinting is false****
>>
>> INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 266)
>> Global memtable threshold is enabled at 339MB****
>>
>> DEBUG [main] 2013-01-03 14:08:58,008 DatabaseDescriptor.java (line 381)
>> setting auto_bootstrap to true****
>>
>> ERROR [main] 2013-01-03 14:08:58,024 DatabaseDescriptor.java (line 495)
>> Fatal configuration error****
>>
>> org.apache.cassandra.exceptions.ConfigurationException: For input string:
>> "85070591730234615865843651857942052863"****
>>
>> at
>> org.apache.cassandra.dht.Murmur3Partitioner$1.validate(Murmur3Partitioner.java:180)
>> ****
>>
>> at
>> org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:433)
>> ****
>>
>> at
>> org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:121)
>> ****
>>
>> at
>> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:178)
>> ****
>>
>> at
>> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:397)
>> ****
>>
>> at
>> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440)
>> ****
>>
>> ****
>>
>> ****
>>
>> This looks like a bug.****
>>
>> ****
>>
>> Thanks****
>>
>> ****
>>
>> ****
>>
>> ** **
>>
>> ----------------------------------
>> Join Barracuda Networks in the fight against hunger.
>> To learn how you can help in your community, please visit:
>> http://on.fb.me/UAdL4f ****
>>
>> ****
>>
>> ----------------------------------
>> Join Barracuda Networks in the fight against hunger.
>> To learn how you can help in your community, please visit:
>> http://on.fb.me/UAdL4f
>>
>>
>
>
Re: Specifying initial token in 1.2 fails
Posted by Nick Bailey <ni...@datastax.com>.
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.
http://www.datastax.com/docs/1.2/initialize/token_generation#calculating-tokens-for-the-murmur3partitioner
On Fri, Jan 4, 2013 at 10:53 AM, Michael Kjellman
<mk...@barracuda.com>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.
>
> http://www.mail-archive.com/user@cassandra.apache.org/msg26789.html<http://permalink.gmane.org/gmane.comp.db.cassandra.user/30182>
>
> 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 <Dw...@genesyslab.com>
> Reply-To: "user@cassandra.apache.org" <us...@cassandra.apache.org>
> Date: Friday, January 4, 2013 8:48 AM
> To: "'user@cassandra.apache.org'" <us...@cassandra.apache.org>
> Subject: RE: Specifying initial token in 1.2 fails
>
> Michael****
>
> ** **
>
> 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 [mailto:mkjellman@barracuda.com<mk...@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 <Dw...@genesyslab.com>
> *Reply-To: *"user@cassandra.apache.org" <us...@cassandra.apache.org>
> *Date: *Friday, January 4, 2013 8:36 AM
> *To: *"'user@cassandra.apache.org'" <us...@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 following is observed:****
>
> ****
>
> INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 203)
> disk_failure_policy is stop****
>
> DEBUG [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 205)
> page_cache_hinting is false****
>
> INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 266)
> Global memtable threshold is enabled at 339MB****
>
> DEBUG [main] 2013-01-03 14:08:58,008 DatabaseDescriptor.java (line 381)
> setting auto_bootstrap to true****
>
> ERROR [main] 2013-01-03 14:08:58,024 DatabaseDescriptor.java (line 495)
> Fatal configuration error****
>
> org.apache.cassandra.exceptions.ConfigurationException: For input string:
> "85070591730234615865843651857942052863"****
>
> at
> org.apache.cassandra.dht.Murmur3Partitioner$1.validate(Murmur3Partitioner.java:180)
> ****
>
> at
> org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:433)
> ****
>
> at
> org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:121)
> ****
>
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:178)
> ****
>
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:397)
> ****
>
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440)
> ****
>
> ****
>
> ****
>
> This looks like a bug.****
>
> ****
>
> Thanks****
>
> ****
>
> ****
>
> ** **
>
> ----------------------------------
> Join Barracuda Networks in the fight against hunger.
> To learn how you can help in your community, please visit:
> http://on.fb.me/UAdL4f ****
>
> ****
>
> ----------------------------------
> Join Barracuda Networks in the fight against hunger.
> To learn how you can help in your community, please visit:
> http://on.fb.me/UAdL4f
>
>
Re: Specifying initial token in 1.2 fails
Posted by Michael Kjellman <mk...@barracuda.com>.
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.
http://www.mail-archive.com/user@cassandra.apache.org/msg26789.html<http://permalink.gmane.org/gmane.comp.db.cassandra.user/30182>
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 <Dw...@genesyslab.com>>
Reply-To: "user@cassandra.apache.org<ma...@cassandra.apache.org>" <us...@cassandra.apache.org>>
Date: Friday, January 4, 2013 8:48 AM
To: "'user@cassandra.apache.org<ma...@cassandra.apache.org>'" <us...@cassandra.apache.org>>
Subject: RE: Specifying initial token in 1.2 fails
Michael
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 [mailto:mkjellman@barracuda.com]
Sent: Friday, January 04, 2013 8:39 AM
To: user@cassandra.apache.org<ma...@cassandra.apache.org>
Subject: Re: Specifying initial token in 1.2 fails
Murmur3 != MD5 (RandomPartitioner)
From: Dwight Smith <Dw...@genesyslab.com>>
Reply-To: "user@cassandra.apache.org<ma...@cassandra.apache.org>" <us...@cassandra.apache.org>>
Date: Friday, January 4, 2013 8:36 AM
To: "'user@cassandra.apache.org<ma...@cassandra.apache.org>'" <us...@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 following is observed:
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 203) disk_failure_policy is stop
DEBUG [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 205) page_cache_hinting is false
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 266) Global memtable threshold is enabled at 339MB
DEBUG [main] 2013-01-03 14:08:58,008 DatabaseDescriptor.java (line 381) setting auto_bootstrap to true
ERROR [main] 2013-01-03 14:08:58,024 DatabaseDescriptor.java (line 495) Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: For input string: "85070591730234615865843651857942052863"
at org.apache.cassandra.dht.Murmur3Partitioner$1.validate(Murmur3Partitioner.java:180)
at org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:433)
at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:121)
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:178)
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:397)
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440)
This looks like a bug.
Thanks
----------------------------------
Join Barracuda Networks in the fight against hunger.
To learn how you can help in your community, please visit: http://on.fb.me/UAdL4f
Southfield Public School students safely access the tech tools they need on and off campus with the Barracuda Web Filter.
Quick installation and easy to use- try the Barracuda Web Filter free for 30 days: http://on.fb.me/Vj6JBd
RE: Specifying initial token in 1.2 fails
Posted by Dwight Smith <Dw...@genesyslab.com>.
Michael
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 [mailto:mkjellman@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 <Dw...@genesyslab.com>>
Reply-To: "user@cassandra.apache.org<ma...@cassandra.apache.org>" <us...@cassandra.apache.org>>
Date: Friday, January 4, 2013 8:36 AM
To: "'user@cassandra.apache.org<ma...@cassandra.apache.org>'" <us...@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 following is observed:
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 203) disk_failure_policy is stop
DEBUG [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 205) page_cache_hinting is false
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 266) Global memtable threshold is enabled at 339MB
DEBUG [main] 2013-01-03 14:08:58,008 DatabaseDescriptor.java (line 381) setting auto_bootstrap to true
ERROR [main] 2013-01-03 14:08:58,024 DatabaseDescriptor.java (line 495) Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: For input string: "85070591730234615865843651857942052863"
at org.apache.cassandra.dht.Murmur3Partitioner$1.validate(Murmur3Partitioner.java:180)
at org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:433)
at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:121)
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:178)
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:397)
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440)
This looks like a bug.
Thanks
----------------------------------
Join Barracuda Networks in the fight against hunger.
To learn how you can help in your community, please visit: http://on.fb.me/UAdL4f
Re: Specifying initial token in 1.2 fails
Posted by Michael Kjellman <mk...@barracuda.com>.
Murmur3 != MD5 (RandomPartitioner)
From: Dwight Smith <Dw...@genesyslab.com>>
Reply-To: "user@cassandra.apache.org<ma...@cassandra.apache.org>" <us...@cassandra.apache.org>>
Date: Friday, January 4, 2013 8:36 AM
To: "'user@cassandra.apache.org<ma...@cassandra.apache.org>'" <us...@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 following is observed:
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 203) disk_failure_policy is stop
DEBUG [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 205) page_cache_hinting is false
INFO [main] 2013-01-03 14:08:57,774 DatabaseDescriptor.java (line 266) Global memtable threshold is enabled at 339MB
DEBUG [main] 2013-01-03 14:08:58,008 DatabaseDescriptor.java (line 381) setting auto_bootstrap to true
ERROR [main] 2013-01-03 14:08:58,024 DatabaseDescriptor.java (line 495) Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: For input string: "85070591730234615865843651857942052863"
at org.apache.cassandra.dht.Murmur3Partitioner$1.validate(Murmur3Partitioner.java:180)
at org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:433)
at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:121)
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:178)
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:397)
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440)
This looks like a bug.
Thanks
Southfield Public School students safely access the tech tools they need on and off campus with the Barracuda Web Filter.
Quick installation and easy to use- try the Barracuda Web Filter free for 30 days: http://on.fb.me/Vj6JBd