Stop or start a node's cloud machine
A node Jaah launched in your own cloud account runs on a machine your cloud bills you for while it runs. When you won't need the node for a while, stop the machine. The node goes offline and takes no tasks until you start it again. Its disk, type and worktrees stay.
Who can do this: the org admin role, on a node Jaah launched in your cloud, where your plan allows managing that cloud's machines. A machine you run yourself is stopped the way you always stop it. A node that belongs to a node group shows no Stop or Start: the group starts and stops its nodes.
Stop the machine
- In the sidebar, select Directory, then the Machines tab.
- Select the node's name. Its details open on the Overview tab.
- Find the section named for its cloud, for example AWS machine. Its State reads Running.
- Select Stop.
- Stop machine? asks first: the node goes offline until started. Select Stop.
- If tasks are running on the node, Force stop? opens next and lists them. Select Force stop to stop the machine anyway: their runs stop and they go back to Ready. Or select Cancel and wait for them to finish.
- Watch State: it shows Stopping…, then Stopped.
To let running tasks finish first, drain the node and stop it once it is idle.
Start the machine again
- Open the node's details on the Overview tab, as above.
- In the cloud's section, check that State reads Stopped or Stopping…. Start shows only then.
- Select Start. No confirmation is asked.
- Watch State: it shows Starting…, then Running.
- Wait a few minutes for the node to reconnect, then check that its dot is green: see Read a node's status.
If either one fails, a line in the section says Couldn’t stop or Couldn’t start and the node's name. While a change to the machine's type is in progress, neither button shows.
Related
- Restart a node: reboot the machine instead of stopping it.
- Change a cloud node's machine type or disk: resize the machine from the same section.
- Machines: every field and button in the cloud's section.