Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

nodeos will not stay in sync on 2.0.0-rc2 #8228

Closed
matthewdarwin opened this issue Nov 19, 2019 · 4 comments
Closed

nodeos will not stay in sync on 2.0.0-rc2 #8228

matthewdarwin opened this issue Nov 19, 2019 · 4 comments

Comments

@matthewdarwin
Copy link

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

wasm-runtime = eos-vm-jit
eos-vm-oc-enable = true
database-map-mode = locked

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.

@sampleblood
Copy link

is this issue solved?

@matthewdarwin
Copy link
Author

Work in progress. See #8229

@matthewdarwin
Copy link
Author

The PR referenced above definitely helps.

@heifner
Copy link
Contributor

heifner commented Dec 4, 2019

Resolved by #8229

@heifner heifner closed this as completed Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants