How to perform a rolling cold restart through AKO

Context

In some instances, it may be beneficial to perform a cold restart. For example, if we wanted to remove a set from a namespace we need to perform a cold restart on the nodes in a rolling fashion after performing a truncate on the set to effectively remove the metadata of the set.

Reference How to clear up set names when they exceed the limit.

---

Method

We can issue a cold restart by modifying the podSpec. For example, we can add an annotation for the pod(s) which will modify the custom resource (CR) effectively triggering an event for the operator to restart the pods.

 

Example:

podSpec:  
  multiPodPerHost: false  
  metadata:  
    annotations:  
      test: delete-set

kubectl apply -f aerospike_cluster.yaml -n aerospike

By adding the annotations "test: delete-set" into the yaml and reapplying the CR we are modifying the cluster in a way that will invoke the Operator to recreate the pods in a rolling fashion. The Operator also will check for migrations, and not proceed onto the next pod until the migrations are completed successfully.

 

---

Notes

You can monitor the status of migrations by connecting to the cluster through asadm. Additional details on how to perform this can be found on documentation on Connectng to Aerospike cluster

Additional details on the podSpec parameters can be found in Cluster Configuration settings

---

Applies To Earliest Version

Pre 4.9

---

Applies To Latest Version

Current Version

---