This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Background verifier sometimes goes back #9300
Labels
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
Milestone
Comments
Tbaut
added
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
labels
Aug 8, 2018
Thanks for the report, I've seen this happening on mainnet also (cf this comment) |
I'm actually seeing this trying to sync archive + trace node from ethereum mainnet.
For some reason, in this case it only happens when you restart a node that has synced a lot of blocks already. |
This was referenced Aug 20, 2018
Will do, thanks |
Hi @andresilva
and again a lot of messages with |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
M4-core ⛓
Core client code / Rust.
We run a POA-based networks (sokol and core). After upgrade to 1.11.8 I'm getting hard time syncing with the network using warp-sync.
After all snapshots were downloaded, a verifier in the background starts processing blocks (if I understand correctly), here's a piece of log:
As you can see it goes
1345587 -> 1375534
and then drops to8636
. This can happen multiple times, so it's hard to get the verification process to complete. It happens on different block numbersTo test it yourself, please use our spec.json and list of reserved peers
The text was updated successfully, but these errors were encountered: