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
While this is fine for syncing intermittently where your node is already in sync, it gets a notification from one of its closest connected peers that it's behind, it should sync to that peer.
On start up this is different, the node should wait a bit and make a bit more informed decision on what peer to sync from and perhaps select a list.
The text was updated successfully, but these errors were encountered:
Description
---
Allow syncing from multiple peers initially
Motivation and Context
---
See issue: #5852
This allows a node to wait until it gets 5 ChainMetaData during initial
sync until it goes to header sync.
How Has This Been Tested?
---
Unit tests
Fixes: #5852
Sync is always done with a single peer.
While this is fine for syncing intermittently where your node is already in sync, it gets a notification from one of its closest connected peers that it's behind, it should sync to that peer.
On start up this is different, the node should wait a bit and make a bit more informed decision on what peer to sync from and perhaps select a list.
The text was updated successfully, but these errors were encountered: