The Status column on Replica nodes says whether each node is carrying your engine's load; only Online nodes are.
- Online: the node is up and serving the engine.
- Offline: the node is down. Once it has been down for 15 minutes, a notice above the table says so and, for the engine owner, offers Replace node.
- Provisioning: a node you just added is still being set up. Its CPU, memory and disk readings appear once the machine boots and starts reporting.
- Syncing: the node is online but still catching up with the engine's state, so it is not ready to carry load yet.
- Starting: the engine as a whole has not reported its first readings yet, which is normal right after it is created.
- Loading: the console has no reading for this node yet.
- Decommissioning: the node is leaving the engine. After a swap it stays listed under its replacement, labelled "Replaced by …", until the new node is ready to carry the load; then the row disappears.
- Queued: during a node class upgrade, the node is waiting its turn. The upgrade brings in one node at a time.
- Reserved: the node has been replaced and no longer serves, but it is still billed to the end of the period already paid for.
Good to know
- Hover Syncing, Queued, Reserved or Decommissioning in the table for the explanation, or click the row: the details repeat the status and its explanation.
- A node you add normally goes Provisioning, then Syncing, then Online; syncing takes a few minutes.
- While a node is still syncing, you can't add or replace another node, or start a class upgrade. The page tells you when you can.
- A Node change in progress banner above the table lists the adds, removals and swaps you sent from this browser tab that have not finished yet.