Skip to content

[Forknet] State parts GC #12916

Open
Open
@VanBarbascu

Description

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.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions