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

Ability to specify wait time #263

Closed
emmetog opened this issue May 21, 2024 · 0 comments
Closed

Ability to specify wait time #263

emmetog opened this issue May 21, 2024 · 0 comments

Comments

@emmetog
Copy link

emmetog commented May 21, 2024

Sometimes the copy-twice-name strategy needs more time to complete because of dynamically provisioned volumes, 60 seconds is often just at the limit of what it needs. Would be nice to be able to specify a bigger wait time like this for example:

korb data-postgresql-0 --source-namespace default --new-pvc-storage-class new-csi-ratain --strategy copy-twice-name --timeout 360

Here's a timeout on my setup:

...
DEBU[0060] Pod not in correct state yet                  component=mover-job phase=Pending
DEBU[0060] Pod not in correct state yet                  component=mover-job phase=Pending
WARN[0060] failed to wait for pod to be running          component=mover-job error="timed out waiting for the condition"
WARN[0060] Failed to move data                           component=strategy error="pod not in correct state" strategy=copy-twice-name
INFO[0060] Cleaning up...                                component=strategy strategy=copy-twice-name
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