-
Notifications
You must be signed in to change notification settings - Fork 687
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
fix: Document HeaderSync #10280
fix: Document HeaderSync #10280
Conversation
It solves the problem of nodes going into header sync or body sync for just a few seconds. It's not a problem for an rpc node, but for a validator that is enough to miss production of a chunk or a block. Short syncs are not shown in prometheus due to the large poll interval.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the comments and the new structure!
LGTM
SyncStatus::NoSync | SyncStatus::AwaitingPeers | SyncStatus::EpochSync { .. } => { | ||
// TODO: How can it get to EpochSync if it's hardcoded to go from NoSync to HeaderSync? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @posvyatokum I guess
some more epoch sync questions below too
// TODO: This function should check the difference between the current header_head height and the highest height of the peers. | ||
// TODO: Triggering header sync to get 1 header (or even 0 headers) makes little sense. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe ramp up for @telezhnaya ?
@@ -225,7 +225,7 @@ pub struct ClientConfig { | |||
pub header_sync_progress_timeout: Duration, | |||
/// How much time to wait before banning a peer in header sync if sync is too slow | |||
pub header_sync_stall_ban_timeout: Duration, | |||
/// Expected increase of header head weight per second during header sync | |||
/// Expected increase of header head height per second during header sync |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol
97dc1f5
to
6299b01
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #10280 +/- ##
==========================================
- Coverage 71.78% 71.78% -0.01%
==========================================
Files 712 712
Lines 142858 142878 +20
Branches 142858 142878 +20
==========================================
+ Hits 102553 102565 +12
- Misses 35594 35607 +13
+ Partials 4711 4706 -5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Made no functional changes except:
made_enough_progress()
to make the code much simpler to understand.