-
Notifications
You must be signed in to change notification settings - Fork 932
Add a guide to partially reconstruct historic states to Lighthouse book #7679
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
Conversation
|
Some required checks have failed. Could you please take a look @chong-he? 🙏 |
|
This pull request has merge conflicts. Could you please resolve them @chong-he? 🙏 |
book/src/faq.md
Outdated
| "state_upper_limit": "10485760", | ||
| ``` | ||
|
|
||
| Lighthouse will now start to reconstruct the historic states from `slot 10485760`. At this point, if you do not want a full state reconstruction, you may remove the flag `--reconstruct-historic-states`. When the process is completed, you will have the state data from `slot 10485760`. |
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.
So if I'm understanding correctly, the flag --reconstruct-historic-states is only necessary here to "trick" the database into thinking it is going to perform state reconstruction and so doesn't prune states? Otherwise this is just effectively checkpoint syncing to an older state and then syncing forwards as normal (minus state pruning). Does that mean that over time you'd have to repeat these steps to control state db growth?
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.
Yeah, once you sync like this your node keeps all states newer than the checkpoint. In practice it shouldn't be too bad, because state diffs are magic, but I guess users doing this are really interested in saving space. We could add a note along these lines?
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.
If state pruning is already disabled with the flag --reconstruct-historic-states, how to prune states again? Is it done via the manual pruning steps?
So if saving space is a goal, then have to kind of do the manual state pruning from time to time? Because once --reconstruct-historic-state is used, automatic state pruning will not be active for the database from my understanding
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.
Yeah I added some text at the end here which just says to repeat the process
|
Updated the binary installation page 8076ca7 as Lighthouse now supports aarch-apple binary built since v7.1.0: |
…ok (sigp#7679) The main change is adding a guide to partially reconstruct historic states to the FAQ. Other changes: - Update the database scheme info - Delete the Homebrew issue as it has been solved in Homebrew/homebrew-core#225877 - Update default gas limit in: [7cbf7f1](sigp@7cbf7f1) - Updated the binary installation page [8076ca7](sigp@8076ca7) as Lighthouse now supports aarch-apple binary built since v7.1.0
Proposed Changes
The main change is adding a guide to partially reconstruct historic states to the FAQ.
Other changes: