We need to complete migrate an aerospike cluster from one network to the other in Google Cloud. We are currently using local SSD for data storage with indexes in memory. For the migration, we need to delete the old nodes and create new nodes in the new network. We are planning to add shadow disks in the existing clusters and once they are synced, and start the new cluster in the new network using the shadow disks. During the tests, when we started the nodes in new cluster one-by-one and partition migrations started happening as soon as new nodes joining the cluster. Since we already know that new nodes are going to come up with data in a few minutes, is there any way to delay/avoid the partitions migrations between the already started nodes? Ideally, there should not be any migrations as we know that in a matter of a few minutes all nodes will join the cluster with properly distributed partitions.