You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case we can't fix the root causes for nodes getting stuck, we should provide a fully automated workaround e.g. a cron job that check every few minutes the block number returned by localhost:4201 and the block number returned by the load balancer and restarts the container if the node seems to be stuck while the network is progressing.
The text was updated successfully, but these errors were encountered:
In case we can't fix the root causes for nodes getting stuck, we should provide a fully automated workaround e.g. a cron job that check every few minutes the block number returned by localhost:4201 and the block number returned by the load balancer and restarts the container if the node seems to be stuck while the network is progressing.
The text was updated successfully, but these errors were encountered: