-
Notifications
You must be signed in to change notification settings - Fork 220
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: add decision step between header sync and pruned/archival (#3546)
Description --- - removes pruned metadata sync logic from listening state - adds `DecideNextSync` step that is responsible for finding a suitable peer for block/pruned sync - chain metadata service includes peer latency - DRY'd up chain metadata service ping/pong event handling - take latency into account when selecting a sync peer - header sync orders the peers in ascending latency order Motivation and Context --- When transitioning to header sync, the listening state would filter out peers that have a suitable horizon height. However any peer regardless of pruned height can provide headers for header sync. How Has This Been Tested? --- Sync tests Manually
- Loading branch information
Showing
16 changed files
with
349 additions
and
228 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.