-
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
add prune ancient feature #862
Conversation
Besides, can you evaluate how this feature impacts the tx index system? |
It has no effect. It has been fixed for the online problem (that is, the tx index error reported from ancient data after executing the pruneblock tool). The fix is to check whether the block range that needs to be indexed is in ancient before creating the index. If it is not, it will Adjust the boundaries of the block range. |
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.
LGTM
batch.Reset() | ||
|
||
// Step into the future and delete and dangling side chains | ||
if frozen > 0 { |
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.
this code is quite risky, it could even delete the whole chain, is the "dangling" was created with a bug, such as issue: #2529
Maybe we don't need it, as we have already deleted the "dangling" block from first to frozen.
Description
Block Data no longer transfer to AncientDB when delete from KVStore.
Save more os resources, disk space, disk bandwidth, cpu.
Rationale
Release more disk space, disk bandwidth resources.
Example
"./geth" start command add "--puneancient" parameter
Changes
Notable changes: