Skip to content
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

Support step-by-step stage sync #112

Merged
merged 2 commits into from
Jun 1, 2023
Merged

Conversation

calmbeing
Copy link

Support step-by-step stage sync, like step is 1, stage sync will sync block one by one

@@ -271,6 +271,8 @@ type HeaderDownload struct {
posDownloaderTip common.Hash // See https://hackmd.io/GDc0maGsQeKfP8o2C7L52w
badPoSHeaders map[common.Hash]common.Hash // Invalid Tip -> Last Valid Ancestor
stageSyncUpperBound uint64 // Upper bound for stage sync, stop sync upon reached this height
stageSyncStep uint64 // Step size of stage sync, e.g: if it's 1, then will sync block by block
stageSyncStepLeft uint64 // Left Step size of stage sync
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not just update stageSyncUpperBound for each step? then no need this flag: stageSyncStepLeft

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think stageSyncUpperBound is the height which would be suppressed and will be stuck without processing. Step is another feature that can control the stage sync period. They're two different features, right?

@calmbeing calmbeing merged commit 425ddf2 into node-real:devel Jun 1, 2023
1 of 5 checks passed
blxdyx added a commit to blxdyx/bsc-erigon that referenced this pull request Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants