-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
v2.61.0 slow to sync on sepolia #13457
Comments
8+ hours later, it seems to be stuck here:
Note that when it started, it only needed to catch up from block from 7496738 to 7497695 (957 blocks), ie a very small range:
|
Downgrading to v2.60.10, all the steps above completed in about 20mins (and the rest fairly quickly in 7mins):
|
@keithchew can you provide all the flags you used? |
@antonis19 here are the flags I am using:
|
Hmm, I have 2 other nodes on mainnet, which the upgrade went fine last week. But today, one of them is lagging behind, and very slow to catch up:
It is interesting that it looks like each block is being handled twice? A restart did not help, and the same logs as above appears. Reverting back to v2.60.10 works, it catches up fast and without issues. It might not be related to this sepolia bug, but will keep monitoring... |
Can you try setting |
@antonis19 I have updated to 5G, and it is still painfully slow. It is similar to the mainnet logs above, ie each block is processed twice. And there are these strange
I have seen some recent issues regarding erigon3 that is broken with externalcl, I wonder if v2.61.0 pulled some work from e3 which is now causing issues with e2? |
Are you running with external CL? If so which one is it? I am getting around 400 mgas/s running with internal CL btw. |
Trying to upgrade from v2.60.10 to v2.61.0. It is trying to catch up with the latest block, but very very slow:
Rolling back to v2.60.10, it catches up quickly. Is there a regression issue?
The text was updated successfully, but these errors were encountered: