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

Copy finished data to secondary scratch #10

Open
soichih opened this issue Oct 14, 2017 · 0 comments
Open

Copy finished data to secondary scratch #10

soichih opened this issue Oct 14, 2017 · 0 comments

Comments

@soichih
Copy link
Contributor

soichih commented Oct 14, 2017

(Consider)

We create a copy of finished data when child task tries to process the data. But we don't proactively create a copy in case the resource created the data goes off line. This happens more often than not.

Another use case to consider is when a cluster has a very limited scratch space and data that task points to is removed much sooner than we'd like.

When a job finishes, we could automatically rsync the content to configured secondary storage (such as Wrangler).

Wrangler

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

No branches or pull requests

1 participant