Skip to content
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

Closed
Tracked by #1419
xmonader opened this issue Aug 2, 2022 · 6 comments
Closed
Tracked by #1419

STORY: new QSFS version (for TFGrid v3.9.0) #1277

xmonader opened this issue Aug 2, 2022 · 6 comments
Assignees
Milestone

Comments

@xmonader
Copy link
Contributor

xmonader commented Aug 2, 2022

  • QSFS can use some more testing
  • need to understand better how to use in Kubernetes, VM, …
  • need to check the edge cases & document if changes are required
  • example script how to deploy Minio on top of QSFS
@sasha-astiadi sasha-astiadi changed the title QSFS STORY: QSFS 3.7.0 Aug 5, 2022
@ramezsaeed ramezsaeed mentioned this issue Aug 8, 2022
59 tasks
@maxux
Copy link
Contributor

maxux commented Aug 10, 2022

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 QSFS with default behavior, this is a 100% size waste (file is stored 2 times on the backend). There is a workaround by mounting the temp directory to a local disk and not over QSFS to avoid this but this present more things to take in account when deploying a solution.

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 0-db directly and use the full power of 0-stor without overhead.

@maxux
Copy link
Contributor

maxux commented Aug 17, 2022

I'm going to do some research on that anytime soon :)

@xmonader
Copy link
Contributor Author

moved out from 3.7 to 3.8

@despiegk despiegk changed the title STORY: QSFS 3.7.0 STORY: QSFS 3.8.0 Aug 23, 2022
@sasha-astiadi sasha-astiadi changed the title STORY: QSFS 3.8.0 STORY: new QSFS version (for TFGrid v3.8.0) Oct 4, 2022
@ramezsaeed ramezsaeed mentioned this issue Oct 18, 2022
16 tasks
@scottyeager
Copy link

Would be nice to see self healing features back on the roadmap, and some other thoughts:

  • Is self healing possible without an external daemon? Can TF Chain itself handle provisioning new zdbs if some go offline?
  • Should be able to maintain an "x of y" redundancy scheme across a set of prespecified nodes
  • Maybe under new provisioning schemed for wake on LAN, this becomes easier since contracts are with farms rather than nodes?
  • Currently an existing QSFS can't be mounted to new VM. That probably needs to change so data can be recovered on a different VM
  • QSFS support in the playground

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

@despiegk despiegk added this to the 3.9 milestone Nov 15, 2022
@despiegk despiegk changed the title STORY: new QSFS version (for TFGrid v3.8.0) STORY: new QSFS version (for TFGrid v3.9.0) Nov 15, 2022
@despiegk
Copy link
Contributor

first need to do #1345

@xmonader xmonader assigned LeeSmet and unassigned xmonader Nov 23, 2022
@despiegk
Copy link
Contributor

about self healing, I believe there are some as part of the zstor...
need to have more details

@rkhamis rkhamis modified the milestones: 3.9, later, 3.10 Mar 13, 2023
@ramezsaeed ramezsaeed mentioned this issue Apr 6, 2023
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

No branches or pull requests

6 participants