-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URGENT - Archive node with latest snapshot cannot reach live #11306
Comments
I'm also trying without the "--l2.enginekind=reth" option and the node can only recover one block every 2/3 seconds, it's extremely slow considering how the Base chain is going at the moment, to get back live with a node 1 day behind, it takes about 1 week
|
Hi @MrFrogoz , what hardware are you running this on? Specifically, what kind of disk, cpu, and total ram? |
Oracle VM AMD 16 Core, 64 GB Ram, Nvme 25K IOPS. Usage when running: CPU 3% - RAM 30% - DISK 40% I/O sum(R/W) I run many nodes of different blockchains with the same hardware, only Base has slowness issues with blocks sync |
Describe the bug
When the node is set with "--l2.enginekind=reth" and starts downloading from a checkpoint to a target, at this point it is very slow:
and when he finishes a set of blocks, he is still always a couple of hours behind and starts again with a new set of blocks. He does this for days without ever catching up to live.
Steps to reproduce
Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
latest
What database version are you on?
latest
Which chain / network are you on?
base
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: