upgrading - Rejoin Part 2
Re-join the layer1
nodectl will now attempt to join the dag-l1.
For the purpose of this upgrade (document/manual) example, we did not choose the -w (watch) mode. nodectl will not wait for all peers to connect, as it is not necessary to complete the upgrade.
Check seed list again and prepare the node
----- * CHECK SEED LIST REQUEST * ------
Node found on Seed List ....................... True
Building environment .......................... complete
Updating services file ........................ complete
Start request initiated [node_l1] ............. complete
Fetching Status [dag-l1] ......................
Show Status
dag-l1 active (running) ReadyToJoin
PUBLIC API TCP P2P API TCP CLI API TCP
9010 9011 9012
CURRENT SESSION FOUND SESSION ON NETWORK
1702307070372 SessionNotFound ReadyToJoin
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 58M 1S
NODE ID
12345...12345
Identify if we are ready to join
nodectl identified that we are in ReadyToJoin state, so we can initiate the join for layer1.
Please wait while [dag-l1] attempts to join the network.
NOTE ml0 or ml1 networks will not join the Hypergraph until its gl0 or ml0 linked profile changes to Ready state, this could take up to a few minutes.
Prepare join process
nodectl starts the process that allows us to join layer1.
Reviewing [dag-l1] ............................ ReadyToJoin
DownloadInProgress blocker
Because our node's layer0 process was found in the DownloadInProgress state. We are not able to join layer1.
nodectl will offer you the following options:
| option | description |
|---|---|
| w | wait an extra 30 seconds then check the status again and continue if we are in Ready state, or present this options menu again. |
| s | skip the layer1 join process. This can save you a lot of waiting time. Reviewing the layer0 process randomly on your own time later, and then requesting a join to layer1 once layer0 is in Ready state. Optionally, if you have auto_restart enabled, layer1 will auto join when layer0 is in the proper state. |
| q | not recommended: quit the upgrade and do not go any further. This will skip all other upgrade elements. |
We do not need to hit the enter key, only key press the desired option.
ML0 Link node in [DownloadInProgress] state | not Ready
Press w to wait 30 seconds
Press s to skip join
Press q to quit
KEY press and OPTION
Choosing to wait
We press the w key.
nodectl will wait 30 seconds before trying again
Choosing to skip
After 30 seconds we still did not reach Ready state on our Layer0 cluster. We expect that we may need to wait a few hours for the DownloadInProgress to complete.
This time we press s to skip the layer1 join process.
Layer0 reached Ready
For purposes of this documentation, we will show what will happen in the event you reach Ready state and do not need to skip the layer1 join process.
You can skip directly to show status; to continue with the upgrade documentation.
Verify layer0
The node will make sure the dag-l0 or layer0 is in Ready state. If not in Ready state, the process will not continue.
Begin the join
The node will initiate the join to layer1.
Current Found State [dag-l0] .................. Ready
Join cluster status [dag-l1] .................. Preparing
Max Timer 300 seconds
Peers: 188 Connected: 3 State: Ready Timer: 0
Join process complete ......................... done
IMPORTANT It is ok that the peer count > cluster peer count because watch mode was not chosen by upgrade.
Show Status Again
nodectl will check the status of your node.
dag-l1 active (running) Ready
PUBLIC API TCP P2P API TCP CLI API TCP
9010 9011 9012
CURRENT SESSION FOUND SESSION ON NETWORK
1702306944446 1702306944446 True
CLUSTER START NODE START SYSTEM START
2023-12-11-15:02:24Z 2023-12-06 11:46:32 2023-12-06 11:46:32
CLUSTER UPTIME NODE UPTIME SYSTEM UPTIME
~9D 3H 38M 9S ~1M 20S ~14D 6H 59M 31S
NODE ID IN CONSENSUS
12345...12345 True