I found if I restart one aerospike node, the migration would be triggered. Would warm-restart help in this case?
any change in the Aerospike cluster change will trigger migrations as design. This ensures you have the right copy of the data in balanced manner as per the new state of the cluster. The cold start or warm start doesn’t change this behaviour.
Thanks for your reply. If we need to migrate partitions in any way, what can we get from warm start? Why not drop the old data and start the node as a fresh one?