You can also add a new DC with the desired number of nodes and num_tokens on each node with auto bootstrap disabled, then rebuild the new DC from the existing DC before decommission the existing DC. This method only needs to copy data once, and can copy from/to multiple nodes concurrently, therefore is significantly faster, at the cost of doubling the number of nodes temporarily.

On 16/05/2024 09:21, Gábor Auth wrote:

Is there a newer/easier workflow to change num_tokens in an existing cluster than add a new node to the cluster with the other num_tokens value and decommission an old one, repeat and rinse through all nodes?

Gábor AUTH

Reply via email to