-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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: combination of mutex and memoization is broken #11853
Comments
cc @shmruin Has this been fixed? |
@terrytangyuan , I run this example code both master and release-3.4.11 branch but cannot reproduce the problem. (in my local environment) ![]() |
Thanks for investigating this @shmruin I checked again today on v3.4.11 and I was able to reproduce by submitting 3 workflow at the same time. |
@Paritosh-Anand OK, I see. I can reproduce this error by executing multiple workflows with same key at the same time. |
Fixes argoproj#11853 Signed-off-by: shmruin <[email protected]>
Pre-requisites
:latest
What happened/what you expected to happen?
What happened
We have use cases where we do have memoization and synchronization together for a workflow step.
What is expected to happen
Related issues
#11219 - Mutex check happens after memoization cache check and lock info missing from UI
#11612 - parent level memoization is broken
How to replicate
Run the attached example workflow twice.
Version
v3.4.11
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: