0

I am running a TiKV v7.2.0 cluster, which was deployed with tiup with server_configs.pd.replication.max-replicas: 1 configured in topology. After storing about 8TB of data in the cluster, I edited the config to increase max-replicas to 2 with tiup cluster edit-config [clustername] and applied the change. It went through the nodes and did a rolling re-deploy of the config and restart of services.

I expected my disk usage to double, as it re-balances all the keys and copies each one to another node to match the new replication factor 2. In reality, no disk or network activity occurred and no growth in dataset size.

Perhaps it seems the changed config only affects newly-stored data and not existing? How can I get the cluster to repair or rebalance or whatever is needed to replicate the existing data?

Mike B
  • 1

1 Answers1

0

“max-replicas” can only be prime number(1, 3, or 5). So the setting update has no effect.

billmay
  • 1
  • thanks, this makes sense. however I have now tried setting it to 3, and am left in the same boat: the data didn't automatically rebalance or replicate. Are there manual steps I need to take to get the cluster to rebalance for a change in replication factor to affect an existing cluster? – Mike B Aug 04 '23 at 18:28