51-200
>> >> >> >> >>
>> >> >> >> >> But here comes more questions:
>> >> >> >> >> a) what if I add a new datacenter? Then the token ranges need
>> >> >> >> >> to
>> >> &g
, what about the data associated with the ranges to be
> >> >> >> >> balanced?
> >> >> >> >> move them among DCs?
> >> >> >> >> But that doesn't make sense, because each keyspace would
> specify
> >> &
> >> But that doesn't make sense, because each keyspace would specify
>> >> >> >> its
>> >> >> >> snith and fix the DCs to store then.
>> >> >> >>
>> >> >> >> b) It seems no bene
>> >> >> {dc1, node1} 51-100
> >> >> >> {dc2, node1} 1-50
> >> >> >> {dc2, node1} 51-100
> >> >> >>
> >> >> >> I think this is not a trivial question, because each key would be
> >> >
> >> >> {dc2, node1} 1-50
>> >> >> {dc2, node1} 51-100
>> >> >>
>> >> >> I think this is not a trivial question, because each key would be
>> >> >> hashed to determine the token it belongs to, and
>> >> >
Thanks for your reply. I also think separate rings are more reasonable.
So one ring for one dc is only for c* 1.x or 2.x without vnode?
Check these references:
https://docs.datastax.com/en/archived/cassandra/1.1/docs/initialize/token_generation.html
http://www.luketillman.com/one-token-ring-to-r
Hi,
Each DC has the whole ring, each DC contains a copy of the same data. When you
add replication to a new DC, all data is copied to the new DC.
Within a DC, each range of token is 'owned' by a (primary) node (and replicas
if you have RF > 1). If you add/remove a node in a DC, tokens will be
