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

Read dataone data from hash store #37

Open
trey-stafford opened this issue Dec 18, 2024 · 2 comments
Open

Read dataone data from hash store #37

trey-stafford opened this issue Dec 18, 2024 · 2 comments

Comments

@trey-stafford
Copy link
Member

trey-stafford commented Dec 18, 2024

Dataone uses a hash store. We should be able to mount/access this store directly from argo workflows, which will avoid the need to fetch & download those assets for processing.

@trey-stafford trey-stafford converted this from a draft issue Dec 18, 2024
@trey-stafford trey-stafford moved this to Todo in QGreenland-Net Dec 20, 2024
@trey-stafford
Copy link
Member Author

Question: Can we connect to the DataOne hash store in a local dev environment (Rancher Desktop)? Or can we mock its function in dev?

@mbjones
Copy link

mbjones commented Dec 21, 2024

Yes, you should be able to access a test instance in dev, and you could mock it as well. I think it would be useful to discuss access patterns for datasets so that we can minimize network transfer -- my initial thought is that we should be arranging access such that the workflow is passed object locations via config that it can read from and write to, and other components would be responsible for staging objects. This will likely work well for most datasets.

That said, for exceedingly large datasets, we found that storage management (and using distributed, fast SSD pools with a later results merge step onto shared storage) was essential to preventing massive I/O waits during workflow runs. Happy to discuss our previous findings on bottlenecks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants