When Erigon is using swap space instead of physical memory on a RPI 4B 8g during initial sync [7/16 Execution]. It can take a very long time to shutdown. It might be a good idea to update the service to allow a longer shutdown.
I don't have full logs, but basically it took around 5 minutes to shut down with 14GB of memory used. This is important since if it doesn't save the DB successfully it won't save progress of sync, and really the only way to sync with reasonable speed right now on Erigon is to keep restarting it.
I updated my service to 15 minutes just to be safe, but 10 minutes would probably be sufficent.
When Erigon is using swap space instead of physical memory on a RPI 4B 8g during initial sync
[7/16 Execution]. It can take a very long time to shutdown. It might be a good idea to update the service to allow a longer shutdown.I don't have full logs, but basically it took around 5 minutes to shut down with 14GB of memory used. This is important since if it doesn't save the DB successfully it won't save progress of sync, and really the only way to sync with reasonable speed right now on Erigon is to keep restarting it.
I updated my service to 15 minutes just to be safe, but 10 minutes would probably be sufficent.