-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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: pruneancient freeze from the previous position when the first time #2542
fix: pruneancient freeze from the previous position when the first time #2542
Conversation
2449752
to
1212526
Compare
1212526
to
2fa163d
Compare
core/rawdb/prunedfreezer.go
Outdated
log.Info("Read ancientdb item counts", "items", min) | ||
offset += min | ||
items := head - tail | ||
log.Info("Read ancientdb item counts", "items", items) |
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.
add 'head' and 'tail' info ?
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.
added
May double check this code, see if it is reasonable: bsc/core/rawdb/prunedfreezer.go Lines 84 to 90 in 7194125
|
f3da606
to
6436146
Compare
Description
The first time online pruning is enabled, the freeze() process starts from 0, leading to a large number of log.Error("Canonical hash missing, can't freeze", "number", f.frozen) logs.
In the freezer's database, record FrozenOfAncientFreezer. When online pruning is enabled for the first time, it will continue to freeze from the previous position.
Rationale
tell us why we need these changes...
Example
add an example CLI or API response...
Changes
Notable changes: