upgrading - Go Offline
All the necessary information needed to upgrade our Node has been obtained. The process of upgrading the Node can now start.
Leave the cluster
In most cases, we need to take the Node offline to properly upgrade and restart. nodectl will take the Node off the cluster(s). In the below example, we have two profiles:
dag-l0- Hypergraph Global Layer 0dag-l1- metagraph Currency Layer 1
You will see something similar to the 👇 example (but not exact) as your Node attempts to gracefully leave the Clusters that each profile belongs to.
The leave command can take some time to complete, we need to exercise patience during this process. This is because processes are running on the Node need to be completed, before our request a graceful leave. Once the processes are completed, the Node can properly remove itself from the cluster.
Properly and gracefully leaving the cluster is highly recommended. It will help avoid corrupted snapshots and help relieve stress on the rest of the cluster.
Leaving the cluster for profile ............... dag-l1
Node going [Offline] please be patient......... dag-l1
Leaving the cluster for profile ............... dag-l0
Node going [Offline] please be patient......... dag-l0
Node going [Offline] please be patient......... dag-l1
dag-l1 not out of cluster ..................... Leaving
Node going [Offline] please be patient......... dag-l1
dag-l1 not out of cluster ..................... Leaving
Node going [Offline] please be patient......... dag-l1
dag-l1 not out of cluster ..................... Leaving
Node going [Offline] please be patient......... dag-l1
dag-l1 not out of cluster ..................... Leaving
stop request initiated [node_l1] .............. running
stop request initiated [node_l1] .............. complete
stop request initiated [node_l0] .............. running
stop request initiated [node_l0] .............. complete
Status Display
Once both profiles obtain Offline state, nodectl will confirm this by displaying a node status command.
note
The formatting of the 👇 below output may not directly match your Node's CLI.
dag-l0 inactive (dead) ApiNotReady
PUBLIC API TCP P2P API TCP CLI API TCP
9000 9001 9002
LATEST ORDINAL LAST DLed BLK EXP ORDINAL
1010279 1010279 1010279
CURRENT SESSION FOUND SESSION ON NETWORK
1702306944446 SessionNotFound False
CLUSTER START NODE START SYSTEM START
2023-12-11-15:02:24Z n/a 2023-12-06 11:46:32
CLUSTER UPTIME NODE UPTIME SYSTEM UPTIME
~9D 3H 38M 9S n/a ~14D 6H 54M 1S
NODE ID IN CONSENSUS
unknown False
PROFILE SERVICE JOIN STATE
dag-l1 inactive (dead) ApiNotReady
PUBLIC API TCP P2P API TCP CLI API TCP
9010 9011 9012
LATEST ORDINAL LAST DLed BLK EXP ORDINAL
1010279 1010279 1010279
CURRENT SESSION FOUND SESSION ON NETWORK
1702307070372 SessionNotFound False
CLUSTER START NODE START SYSTEM START
2023-12-11-15:04:30Z n/a 2023-12-06 11:46:32
CLUSTER UPTIME NODE UPTIME SYSTEM UPTIME
~9D 3H 38M 9S n/a ~14D 6H 54M 4S
NODE ID
unknown
Now that the Node is off the cluster(s) it can work on making necessary updates, prior to downloading the new version of Tessellation.