Context
Applying changes to Aerospike configuration by applying a new CRD file through the
Aerospike Kubernetes Operator generally leads to a rolling restart of all nodes in the cluster. Depending on AKO version and the specific changes applied, this could involve either warm restarts or cold starts (new containers) of the nodes, but in either case, this can result in migrations being triggered for each cluster change event.
Method
Although it's not possible to eliminate the restarts in the current version of the AKO (3.2.0 as of this writing), the migrations can be alleviated by keeping
migrate-fill-delay set to a time longer than it takes for a full restart of the cluster in the configuration files. It can be
dynamically changed to 0 during periods when the cluster is not expected to change, to speed up recovery from unexpected cluster changes, or manually changed to 0 by a human operator if such changes occur.
Applies To Earliest Version
Pre 4.9
Applies To Latest Version
Current Version
