-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offload Shuttle data #858
Comments
I wonder if we should do this in a phased approach, by first offloading to our existing SP network. We could examine:
|
It should be in phases. We need to ensure that the CIDs are retrievable in any other "retrieval" providers before we offload. If we can prove this (by pinging?) the retrieval providers, we can delete the CID/content from the blockstore and store the meta information on our database. We should store where the user can look up the CID and we can present it on the frontend. |
Depends on #855
Once a root SP has been established, all of the shuttle data should be offloaded to it, and shuttle data should be emptied.
At this point, shuttles have to be reconfigured as temporary stores that immediate delete their data as soon as the 6+1 deals have been executed.
The text was updated successfully, but these errors were encountered: