Restarting a Storage Node

A restart stops and starts one storage node. It is how an offline node is brought back, and how a change to the storage node configuration or a new SPDK image is picked up on a single node. The operation succeeds once the node reports the status online.

Example of a node restart (restart-node.yaml)

apiVersion: storage.simplyblock.io/v1alpha2
kind: StorageNodeOps
metadata:
  name: restart-worker-1
  namespace: simplyblock
spec:
  nodeRef: simplyblock-cluster-worker-1-0
  action: Restart

Restarting a single storage node

kubectl apply -f restart-node.yaml

Two optional fields apply to a restart. With force, the request carries the force flag of the control plane, and with reattachVolume, the volumes of the node are reattached as part of the restart. A field that is left out is not sent, and the control plane applies its own default.

Example of a forced restart that reattaches the volumes

apiVersion: storage.simplyblock.io/v1alpha2
kind: StorageNodeOps
metadata:
  name: restart-worker-1-forced
  namespace: simplyblock
spec:
  nodeRef: simplyblock-cluster-worker-1-0
  action: Restart
  force: true
  reattachVolume: true

The operation runs the steps Requesting and Awaiting, and it holds with a ClusterNotReady event while the cluster is not active or is rebalancing. An abort is honored only in Requesting, before the restart has been sent.

To restart every node of a cluster instead of one, see Rolling Restart, which sequences the nodes and waits for the rebalancing between them. How an operation is tracked and cleaned up is described in Storage Node Actions.