Currently accountsdb snapshots are stored as full database copies on disk. Without CoW filesystem this takes too much space. Additionally, for the purposes of replication, we need to send those snapshots over the network, which necessitates some form of archiving.
Proposal: every time a snasphot is taken, it should be archived. The replication service can then pick up those snapshots and send them over the network. The original snapshot directory can be removed to save space. The archival should happen in the background to prevent halting the block production.
Currently accountsdb snapshots are stored as full database copies on disk. Without CoW filesystem this takes too much space. Additionally, for the purposes of replication, we need to send those snapshots over the network, which necessitates some form of archiving.
Proposal: every time a snasphot is taken, it should be archived. The replication service can then pick up those snapshots and send them over the network. The original snapshot directory can be removed to save space. The archival should happen in the background to prevent halting the block production.