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

Run Lodestar without persisting archive states at all or minimally #5889

Open
philknows opened this issue Aug 15, 2023 · 4 comments
Open

Run Lodestar without persisting archive states at all or minimally #5889

philknows opened this issue Aug 15, 2023 · 4 comments
Labels
meta-feature-request Issues to track feature requests. scope-ux Issues for CLI UX or general consumer UX.

Comments

@philknows
Copy link
Member

Problem description

For some testnet or dev networks, we do not need to archive any states and there should be a mode that will allow us to enable it. Instead of continually upgrading SSDs on these no-value networks or manually dumping the beacon data periodically, we should just enable this feature.

Solution description

Similar to sigp/lighthouse#3211 on Lighthouse, status-im/nimbus-eth2#4419 on Nimbus and Consensys/teku#6576 on Teku, we should discuss different strategies for how we persist archive states. For Holesky, this will be useful to prevent storing unnecessary information as the network will start at 2x mainnet size.

Additional context

No response

@philknows philknows added the meta-feature-request Issues to track feature requests. label Aug 15, 2023
@philknows philknows added this to the v1.11.0 milestone Aug 15, 2023
@wemeetagain
Copy link
Member

For now this should be possible using --chain.archiveStateEpochFrequency Infinity or --chain.archiveStateEpochFrequency 9999999999. Not great UX but should get the job done for our Holesky nodes.

@philknows philknows added the scope-ux Issues for CLI UX or general consumer UX. label Aug 22, 2023
@philknows
Copy link
Member Author

Will leave this issue open for a better UX solution in the future. But for now, the above flags will do the job! Thanks.

@philknows philknows removed this from the v1.11.0 milestone Aug 22, 2023
@philknows philknows added the meta-discussion Indicates a topic that requires input from various developers. label Oct 15, 2024
@philknows
Copy link
Member Author

What does better UX look like for this feature? Should we implement something similar to other client teams or just add the notable comment by @wemeetagain to our docs?

@philknows
Copy link
Member Author

This may change once we have state diffs and in V2, this may not be the default. Related to #7005

@philknows philknows removed the meta-discussion Indicates a topic that requires input from various developers. label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta-feature-request Issues to track feature requests. scope-ux Issues for CLI UX or general consumer UX.
Projects
None yet
Development

No branches or pull requests

2 participants