-
Notifications
You must be signed in to change notification settings - Fork 36
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
Files failing to copy does not exit the process #8
Comments
For example, we saw this error last night:
And the backup job was sat running since then. In such scenarios, everything should terminate. |
Hi @Tim020 I am experiencing the same problem with copying to GCS. Have you solved this problem? If so, how? If not - where did you see this error? In my case the copy process just hangs forever without any error output at all. |
Hey @rrusmana, unfortunately I haven't been able to solve this. I see this error when copying from K8s to AWS, it encounters an error like the one above and then hangs indefinitely. |
We are seeing the similar problem in our Jenkins backup job. |
I am not sure if this is due to using the parallelism setting or not, however if a file fails to copy (in our case from K8S to AWS) then the parent process is not terminated. This leads to copy jobs sat spinning making no progress for days at a time. The desired behaviour here is that, should a file fail to copy, the entire process should exit with a non-0 status code to allow the copy to be retried if desired.
The text was updated successfully, but these errors were encountered: