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

Mounting fails if too many files are in VFS cache #36

Open
miwig opened this issue Dec 8, 2022 · 0 comments
Open

Mounting fails if too many files are in VFS cache #36

miwig opened this issue Dec 8, 2022 · 0 comments

Comments

@miwig
Copy link

miwig commented Dec 8, 2022

Rclone calls Cache.reload on startup, to check if any files from the VFS cache have to be uploaded. Since this talks to the remote, it can take a long time. After the default --daemon-wait setting of one minute, rclone exits and mounting fails. Increasing --daemon-wait leads to a gRPC timeout after 2 minutes, also causing Kubernetes to see the mount as failed, while the rclone process still exists and now never exits, because NodeUnpublishVolume is never called.

Not running with --daemon and managing the child process manually, as seen here might be a good idea (though it requires checking that the mount was successful), but can't really solve this problem, because we still have to finish mounting before the 2 minute gRPC timeout hits us.

It seems to me that the only solution is to start with a fresh cache each time, which brings its own problems, i.e. data loss.

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