paradigmxyz
Support db initialization when static files are present
Describe the feature
After deleting the db folder and not deleting the static_files folder I received this error:
static files found, but the database is uninitialized. If attempting to re-syncing, delete both.
A potentially good way to run reth would be to use a slow network drive for the static_files, and fast local nvme for the db. Since local storage is ephemeral on aws, occasionally the db will be lost. In this case, it would be very nice to resync with the static_files still present. Additionally this sync could be faster than normal, which would lessen down time after the ephemeral storage is reset.
Perhaps there is something that I'm missing, or a technical reason for the current behaviour.
This issue is stale because it has been open for 21 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Anyone have any thoughts on this? Would be willing to take a stab at implementing if there's demand.
This issue is stale because it has been open for 21 days with no activity.
This issue was closed because it has been inactive for 7 days since being marked as stale.