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

The "move" action deletes the original file even if it failed to be added to the cache #4

Open
hargreaw opened this issue Apr 21, 2023 · 0 comments

Comments

@hargreaw
Copy link
Contributor

When adding a file to the cache and using the "move" action the original file disappears if the file can't be added to the cache if the cache is busy.

Steps to reproduce:

  1. Attempt to add many files to the cache using the "move" mode in parallel
  2. Try to access files that failed to be added to the cache because it was busy

Workaround:
Use the "copy" action, delete original file if successfully added. Not ideal as when dealing with many large files in parallel this could lead to large amounts of temporary data duplication, it is also much slower than a "move" action.

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