Won't option 2 in that list potentially cause some pretty severe load
imbalance in most cases? The last node with 256 tokens will end up with
16x as much data on it as the 16 token nodes, right?
You'd have to mitigate it either by adding 16 new nodes for every one you
replace except the last
Hi Jean,
This is a really good question.
As Erick mentioned, if you want to change your cluster's *num_tokens* to 16
to match the 4.0 default, you will need to perform a datacenter migration.
Feel free to read over this blog post
Great Thank you for the answer and the link!
> On 4 Sep 2021, at 11:35, Erick Ramirez wrote:
>
> It isn't possible to change the tokens on a node once it is already part of
> the cluster. Cassandra won't allow you to do it because it will make the data
> already on disk unreadable. You'll
It isn't possible to change the tokens on a node once it is already part of
the cluster. Cassandra won't allow you to do it because it will make the
data already on disk unreadable. You'll need to either configure new nodes
or add a new DC. I've answered an identical question in
Hi,
We are currently running Cassandra 3.11.11 with the default values for
num_tokens: 256.
We want to migrate to Cassandra 4.0.0 which has default values for num_tokens
set to 16.
Is it safe to migrate with the default values, i.e. can I leave it set to 16
when migrating to Cassandra 4.0.0