Hi,
On Thu, 16 May 2024, 17:40 Bowen Song via user,
wrote:
> Replacing nodes one by one in the existing DC is not the same as replacing
> an entire DC.
>
> For example, if you change from 256 vnodes to 4 vnodes on a 100 nodes
> single DC cluster. Before you start, each node owns ~1% of the
Replacing nodes one by one in the existing DC is not the same as
replacing an entire DC.
For example, if you change from 256 vnodes to 4 vnodes on a 100 nodes
single DC cluster. Before you start, each node owns ~1% of the cluster's
data. But after changing 99 nodes, the last remaining node
Hi,
On Thu, 16 May 2024, 16:55 Jon Haddad, wrote:
> Unless your cluster is very small, using the method of adding / removing
> nodes will eventually result in putting a much larger portion of your
> dataset on a very few number of nodes. I *highly* discourage this.
>
It has ~15 GB data on
Hi,
On Thu, 16 May 2024, 10:37 Bowen Song via user,
wrote:
> 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
>
Unless your cluster is very small, using the method of adding / removing
nodes will eventually result in putting a much larger portion of your
dataset on a very few number of nodes. I *highly* discourage this.
The only correct, safe path is Bowen's suggestion of adding another DC and
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,
Hi.
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?
--
Bye,
Gábor AUTH
