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
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Many block producers run API nodes behind a load balancer. The load balancer will distribute load to multiple nodeos servers. Some nodeos servers might not be up-to-date because they crashed and have to re-sync. In order to not server old data, the server admin should remove the nodeos server from the load balancer until it catches up (or remove the HTTP plugin from config.ini).
It would be easier for server admins, however, if this was automatic.
If there was an option in config.ini such that if nodeos is behind, it will not process requests from HTTP(s) port. This means the load balancer checking script would deem the server "down" and take it out of rotation.
Something like:
# if nodeos is not up-to-date, refuse to handle HTTP transactions.
# Parameter is number of seconds delay that is acceptable
refuse-connection-when-behind = 5
The text was updated successfully, but these errors were encountered:
on https://validate.eosnation.io, I can see many people who's API nodes are running behind. Search for "last block is not up-to-date" in the error report.
Many block producers run API nodes behind a load balancer. The load balancer will distribute load to multiple nodeos servers. Some nodeos servers might not be up-to-date because they crashed and have to re-sync. In order to not server old data, the server admin should remove the nodeos server from the load balancer until it catches up (or remove the HTTP plugin from config.ini).
It would be easier for server admins, however, if this was automatic.
If there was an option in config.ini such that if nodeos is behind, it will not process requests from HTTP(s) port. This means the load balancer checking script would deem the server "down" and take it out of rotation.
Something like:
The text was updated successfully, but these errors were encountered: