You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
state_sync.dump.restart_dump_for_shards
)The text was updated successfully, but these errors were encountered: