-
Notifications
You must be signed in to change notification settings - Fork 152
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
[BUG] Problem with long running phase #1622
Comments
Thanks for opening this issue 👍. The team will review it shortly. If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md. If you haven't already, please take a moment to review our project's Code of Conduct document. |
@ihcsim hi, did you reproduce the problem? |
Hi @blafry, |
@akankshakumari393 Please take this one |
We have started working on the issue, but unfortunately we don't have the resolution yet. I will keep updating the progress here. |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
@akankshakumari393 hello, any progress? |
We were able to reproduce the issue, it happens only in cases where the action keeps running for more than 5 hrs. We are still looking into it. |
This issue is marked as stale due to inactivity. Add a new comment to reactivate it. |
Any updates? |
1 similar comment
Any updates? |
Hi @DCkQ6 , |
In the worst case backup of our problematic huge database takes about 7h |
Thank you, I will make sure that I bring this up in coming community call. |
Hi @viveksinghggits! Any updates after community call? |
Hi @blafry , |
As discussed in today's community meeting, this also came up recently in our Slack channel with a proposed solution. @e-sumin can you take a look? |
Describe the bug
When phase takes about 6 hours, the operator (0.81.0) does not set the
snapshot_id
in theActionSet
despite using kando for this purpose.To Reproduce
Steps to reproduce the behavior:
Blueprint:
ActionSet describe:
Operator logs:
Expected behavior
An artifact has been set, key:
snapshot_id
value:6c1b0940
Environment
Kubernetes Version/Provider: 1.22
Cluster Size (#nodes): 1
Additional context
Instead of
sleep 20000
in my blueprint there is a mysqldump which output is streamed to the restic repository. Due to the size of the database and limited bandwidth, this is how long it takes. In the case of a shorter time, I was unable to reproduce the problem.The text was updated successfully, but these errors were encountered: