ng in a
>> heterogenous storage configuration. In these cases how would it affect
>> efficiency if the token figure were the same across all nodes?
>>
>>
>>
>> From: Elliott Sims
>> Sent: Thursday, June 16, 2022 12:24 AM
>> To: user@cassandra.apache.org
>
fect
> efficiency if the token figure were the same across all nodes?
>
>
>
> *From:* Elliott Sims
> *Sent:* Thursday, June 16, 2022 12:24 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Configuration for new(expanding) cluster and new admins.
>
>
>
> EXTERNAL
>
e thing to watch/consider - the (number of tokens) * (the number of nodes)
makes repairs work harder
Sean R. Durity
INTERNAL USE
-Original Message-
From: Marc Hoppins
Sent: Wednesday, June 15, 2022 3:34 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Configuration for new(expandin
ncy if the
token figure were the same across all nodes?
From: Elliott Sims
Sent: Thursday, June 16, 2022 12:24 AM
To: user@cassandra.apache.org
Subject: Re: Configuration for new(expanding) cluster and new admins.
EXTERNAL
If you set a different num_tokens value for new hosts (the value should ne
If you set a different num_tokens value for new hosts (the value should
never be changed on an existing host), the amount of data moved to that
host will be proportional to the num_tokens value. So, if the new hosts
are set to 32 when they're added to the cluster, those hosts will get twice
as muc
You shouldn't need to change num_tokens at all. num_tokens helps you
pretend your cluster is a bigger than it is and randomly selects tokens for
you so that your data is approximately evenly distributed. As you add more
hosts, it should balance out automatically.
The alternative to num_tokens is
Hi all,
Say we have 2 datacentres with 12 nodes in each. All hardware is the same.
4-core, 2 x HDD (eg, 4TiB)
num_tokens = 16 as a start point
If a plan is to gradually increase the nodes per DC, and new hardware will have
more of everything, especially storage, I assume I increase the num_tok
