For example... just a few minutes ago... I have been off sync by 3 blocks... and because that's enough for me to think I can miss, the script just decided to unregister:
And now (at the time of this comment) its already registered again because I am in sync.
With time I plan to make it more reactive. There are lots I know I can improve.
Did you cause this off sync to test the script?
Hey, the script could be run as a service somewhere :)
No... its probably my lousy ISP and the fact that I am extremely distant from the rest of the world (higher latency). It's very common for the node time to time to not be in full sync with the head of the chain. But still that should not affect the block production if you take the right decisions about when to have the node registered or not (hence my he-awm script)
To be honest, I don't know if this is the code that does not yet know to quickly sync when there is lack or slow response from the Streamer nodes. Do you experience the same or you are always in sync?
I have other stuff running that does not behave like this, so, for now I am yet not 100% sure if this is due network or the P2P code.
I am always in sync. In fact, I am surprised that the node is working so smoothly. (knock knock no jinx :) )
It may help that my VPS resides in Lithuania :)
Most likely... but hence any node can easily become out of sync for a diverse amount of reasons. And to react to that is essential for network stability. That's why I would recommend everyone to use something like the script I created.
Can your script, potentially, be used as a sort of load balancer or node switcher too? So you could switch from one node to the other manually? With some safeguard in place that the switched-to node must be in sync :)
Not yet, but I have plans to add something like that. Either for nodes behind the same IP or behind different IPs.
Great. Imagine the web scoreboard where you can see the health of your nodes and switch them with a click :)