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
There was a case where a node was forked for several hours, stuck on the same block. When the endpoint recovered, hive-sync continued following blocks at a 3s interval but way behind head. Checking head block time would allow us to easily detect this condition. It should be treated the same way as the max-gap check; i.e. exit listen routine and return to fast-sync.
The text was updated successfully, but these errors were encountered:
There was a case where a node was forked for several hours, stuck on the same block. When the endpoint recovered, hive-sync continued following blocks at a 3s interval but way behind head. Checking head block time would allow us to easily detect this condition. It should be treated the same way as the max-gap check; i.e. exit listen routine and return to fast-sync.
The text was updated successfully, but these errors were encountered: