;> only time you might want to distribute this is if your instances are of
>>> different sizing/capability which is also a bad scenario.
>>>
>>> From: Björn Hachmann
>>> Reply-To: "user@cassandra.apache.org"
>>> Date: Friday
enario.
>>
>> From: Björn Hachmann
>> Reply-To: "user@cassandra.apache.org"
>> Date: Friday, 27 March 2015 12:11
>> To: user
>> Subject: Re: Replication to second data center with different number of
>> nodes
>>
>>
>> 201
mailto:user@cassandra.apache.org>>
> Date: Friday, 27 March 2015 12:11
> To: user mailto:user@cassandra.apache.org>>
> Subject: Re: Replication to second data center with different number of nodes
>
>
> 2015-03-27 11:58 GMT+01:00 Sibbald, Charles <mailto:charles.sibb...@bsky
ch node the same number of tokens, the only
> time you might want to distribute this is if your instances are of
> different sizing/capability which is also a bad scenario.
>
> From: Björn Hachmann
> Reply-To: "user@cassandra.apache.org"
> Date: Friday, 27 March 2015
gt;"
mailto:user@cassandra.apache.org>>
Date: Friday, 27 March 2015 12:11
To: user mailto:user@cassandra.apache.org>>
Subject: Re: Replication to second data center with different number of nodes
2015-03-27 11:58 GMT+01:00 Sibbald, Charles
mailto:charles.sibb...@bskyb.com>>:
Cassandra’
2015-03-27 11:58 GMT+01:00 Sibbald, Charles :
> Cassandra’s Vnodes config
Thank you. Yes, we are using vnodes! The num_token parameter controls the
number of vnodes assigned to a specific node.
Might be I am seeing problems where are none.
Let me rephrase my question: How does Cassandra know
I would recommend you utilise Cassandra’s Vnodes config and let it manage this
itself.
This means it will create these and a mange them all on its own and allows
quick and easy scaling and boot strapping.
From: Björn Hachmann
mailto:bjoern.hachm...@metrigo.de>>
Reply-To: "user@cassandra.apache
