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

[Forknet] State parts GC #12916

Open
VanBarbascu opened this issue Feb 12, 2025 · 0 comments
Open

[Forknet] State parts GC #12916

VanBarbascu opened this issue Feb 12, 2025 · 0 comments

Comments

@VanBarbascu
Copy link
Contributor

Due to the short epoch length, the state parts bucket for a forknet can get quite large if the network is not restarted.

This task has a lower priority as we plan to implement full descentralized state sync.

Possible option:

  • Set retention period on the bucket. This has the drawback of not taking into account the time when the network is parked. When the network is resumed, the parts will not be available and the dumper need to be configured to always check if the parts are dumped in the bucket. (state_sync.dump.restart_dump_for_shards)
  • Set a cron job on the dumper node to clear all old epochs in the bucket.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant