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.
When running nodeos 2.0.0-rc2 on EOS Mainnet on a public p2p endpoint with around 30 incoming connections, nodeos will sometimes not stay in sync. It sometimes falls behind by 1 or 2 minutes. After a (a few hours) it will catch up again. It is not predictable what is going on as it is accepting incoming connections from the general public.
Server is not too fast: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
Server has lots of RAM and is using the following configuration
When running nodeos 2.0.0-rc2 on EOS Mainnet on a public p2p endpoint with around 30 incoming connections, nodeos will sometimes not stay in sync. It sometimes falls behind by 1 or 2 minutes. After a (a few hours) it will catch up again. It is not predictable what is going on as it is accepting incoming connections from the general public.
Server is not too fast: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz
Server has lots of RAM and is using the following configuration
This problem was not experienced on 1.8.x. (Although of course EOS Mainnet transaction volume does change). Upgrade to 2.0.0 occurred on Nov 14.
The server is connected to other peers (locally on the same network) that are in sync.
Logs are available if required.
The text was updated successfully, but these errors were encountered: