-
-
Notifications
You must be signed in to change notification settings - Fork 312
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
Peer cronically behind #3110
Comments
Found a Prysm peer that's also cronically behind but consistently sending us the blocks afterwards
|
It's not true I've added more logging and peers are not being according to their status messages. All peers my node connects to, follow the head very closely (get the head block within a 2-3 seconds margin max). So why are they relaying old blocks? |
When this issue was opened we didn't have enough metrics to properly understand what's going on. Now we receive almost all blocks in time, so no longer an issue. Moral of the story: invest in metrics kids, not in random logs in the codebase 👍 |
Describe the bug
Our peer is cronically behind getting blocks very late from mesh peers.
In this logs you can see how three Lighthouse peers discover the same block 60s late and forward to us in sequence:
Scroll down starting at log
Eph 63940/26 6.001 [] info: Synced - block: 2046106
The text was updated successfully, but these errors were encountered: