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 one, or doing several rounds of replacing every node with one that has somewhat fewer tokens. On Sat, Sep 4, 2021, 2:36 AM Erick Ramirez <erick.rami...@datastax.com> 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 need to either configure new nodes > or add a new DC. I've answered an identical question in > https://community.datastax.com/questions/12213/ where I've provided steps > for the 2 options. I hope to draft a runbook and get it published on the > Apache website in the coming days. Cheers! >
