-
Notifications
You must be signed in to change notification settings - Fork 4
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
STORY: new QSFS version (for TFGrid v3.9.0) #1277
Comments
If Minio is used only to provide an S3 interface on top on QSFS, it works (we already did it successfully), but it's extremely inefficient. Minio uses a cache directory on which it stores all data chunks before building the final file by concatenating all chunks together. By using So it's doable, we did it already, if we need a quick working solution it's fine, minio have the advantage to support more protocols and have a nice UI on top. But if we want to support S3, it would be really interesting to build something on top of |
I'm going to do some research on that anytime soon :) |
moved out from 3.7 to 3.8 |
Would be nice to see self healing features back on the roadmap, and some other thoughts:
Someday dreams... a mode where data is never lost, as long as the provisioning wallet has some TFT and there are some node alive somewhere on the Grid. A kind of "set and forget" that doesn't depend on specific nodes or farms, can provision to new nodes that come online, even new farms. This probably is the realm of external daemon, like the twin, that can handle provisioning new capacity on behalf of the user |
first need to do #1345 |
about self healing, I believe there are some as part of the zstor... |
The text was updated successfully, but these errors were encountered: