Skip to main content

Stateful Node Actions

With stateful node actions you can change the node’s state while persisting its resources.

View Configuration​

View the JSON configuration for the stateful node. You can also copy the configuration to the clipboard or export the configuration to a JSON file.

Recycle​

This action is equivalent to rebooting or restarting a machine. The action is relevant to apply changes which were made in the node configuration and then require launching a new node in order to apply them (for example, updating the availability zone list and updating the VM size list). When this action is used, the node is paused, the current VM is terminated and a new VM is launched instead, while saving the original VM resources according to the persistence preferences.

Start​

You can start a Spot-managed VM in the Spot console when a stateful node is stopped.

Stop​

You can stop the Azure VM in the Spot console and in the Azure console when a stateful node is running. The stateful node will detect that the VM is in a stopped status and, by default, move to a stopped state. It might take a few minutes for the stateful node to appear as stopped. If the information from the user who initiated the stop operation is not received within 3 minutes after the virtual machine has stopped, it will be regarded as an interruption.

Use the API to specify an allowlist. When a VM is stopped by a user containing a string on this list, it will not be considered an interruption. If a VM is stopped by anyone not included in the list, it will be considered an interruption. This will help determine the required format for the names in the API. For example, the format could be user.name@email.com, uname@email.com, uname, user.name, or service.

  • If the list is empty, the defined behavior is NONE.
  • If the list is null, the defined behavior is ALL. This applies if the object is not defined.

You cannot resume or delete a stateful node when it is stopped.

Example for stateful node
{
  "statefulNode": {
    "strategy": {
      "vmAdmins": [
        "@example1.com",
        "@example2.com",
       "service1"
      ]
    }
 }
}

Pause​

When this action is used, the node is paused, the current VM is terminated, while saving its original resources according to the persistence preferences.

Resume​

This action starts the node after it was paused. When this action is used, the node will resume, and a new VM will be launched together with the persisted resources that were saved while the node was paused.

Delete​

When you delete a stateful node, you can choose to terminate the VM, revert to on-demand, delete disks, delete snapshots, delete the public IP, and deregister the VM from the load balancer.

  • When Terminate VM is marked, the VM is deregistered from the load balancer.
  • When Terminate VM is not marked, you can choose to delete snapshots, revert it to the on-demand lifecycle, and deregister it from the load balancer.
  • When Delete public IP is marked, Delete network interfaces is marked automatically and cannot be unmarked.

Both the node and the selected resources will be deleted after 96 hours. You can use the Delete Stateful Node API to set a different time period to wait.