This article can be used to temporarily pause migrations on an Aerospike cluster.
Aerospike rebalances data within the cluster in the event of a node joining or leaving or any cluster size changes due to a network glitch. Migration (depending on the configuration) can impact the overall cluster performance. In some situations such as a planned network maintenance, you can use the following configurations to pause migrations.
Note: These configurations will be just pausing migrations. Once the configurations are tuned back to default, migration will resume to rebalance data.
There are the 2 configuration variables which are dynamically configurable on an Aerospike node:
migration-max-num-incoming to 0 should prevent a node from receiving migration traffic.
These are the maximum number of partitions a node at any given time. http://www.aerospike.com/docs/reference/configuration/#migrate-max-num-incoming
asinfo -v "set-config:context=service;migrate-max-num-incoming=0"
migrate-threads to 0 should prevent a node from migrating partitions out.
These are the number of threads per server allocated for data migration. http://www.aerospike.com/docs/reference/configuration/#migrate-threads
asinfo -v "set-config:context=service;migrate-threads=0"
See below documentation to manage and tune migrations: http://www.aerospike.com/docs/operations/manage/migration