fix: add decision step between header sync and pruned/archival #3546
Conversation
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
base_layer/core/src/base_node/state_machine_service/states/sync_decide.rs
Outdated
Show resolved
Hide resolved
sdbondi
force-pushed
the
core-sync-peer-selection-after-header-sync
branch
from
53e622b to
3a002ba
Compare
sdbondi
force-pushed
the
core-sync-peer-selection-after-header-sync
branch
from
3a002ba to
5ab0342
Compare
stringhandler
approved these changes
Nov 9, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
DecideNextSyncstep that is responsible for finding a suitable peer for block/pruned syncMotivation 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