You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we request headers from a peer (something we do only for one peer when we're in IBD, to avoid duplicating it), there is no timeout. If the peer we're asking it from does not respond, we're stuck.
Fix this by adding a timeout, and integrating it in the block fetch timeout logic (because, when we already have outstanding block download requests, we can't header to appear quickly).
The text was updated successfully, but these errors were encountered:
I coded this back in 2013 but it never got merged... I can rebase it if it's now wanted.... It wasn't a fixed timeout but was calculated based on overall latency.
When we request headers from a peer (something we do only for one peer when we're in IBD, to avoid duplicating it), there is no timeout. If the peer we're asking it from does not respond, we're stuck.
Fix this by adding a timeout, and integrating it in the block fetch timeout logic (because, when we already have outstanding block download requests, we can't header to appear quickly).
The text was updated successfully, but these errors were encountered: