Hi Leo,
The token assignment for each node in the cluster must be unique regardless
of the datacenter they are in. This is because the range of tokens
available to assign to nodes is per cluster. Token allocation is performed
per node at a global level. A datacenter helps define the way data is
re
Hi Anthony !
I have a follow-up question :
Check to make sure that no other node in the cluster is assigned any of the
> four tokens specified above. If there is another node in the cluster that
> is assigned one of the above tokens, increment the conflicting token by
> values of one until no oth
Hi Enrico,
Glad to hear the problem has been resolved and thank you for the feedback!
Kind regards,
Anthony
On Mon, 2 Dec 2019 at 22:03, Enrico Cavallin
wrote:
> Hi Anthony,
> thank you for your hints, now the new DC is well balanced within 2%.
> I did read your article, but I thought it was n
Hi Anthony,
thank you for your hints, now the new DC is well balanced within 2%.
I did read your article, but I thought it was needed only for new
"clusters", not also for new "DCs"; but RF is per DC so it makes sense.
You TLP guys are doing a great job for Cassandra community.
Thank you,
Enrico
Hi Enrico,
This is a classic chicken and egg problem with the
allocate_tokens_for_keyspace setting.
The allocate_tokens_for_keyspace setting uses the replication factor of a
DC keyspace to calculate the token allocation when a node is added to the
cluster for the first time.
Nodes need to be add
Hi all,
I have an old datacenter with 4 nodes and 256 tokens each.
I am now starting a new datacenter with 3 nodes and num_token=4
and allocate_tokens_for_keyspace=myBiggestKeyspace in each node.
Both DCs run Cassandra 3.11.x.
myBiggestKeyspace has RF=3 in dcOld and RF=2 in dcNew. Now dcNew is ver