-
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
Mutex check happens after memoization cache check and lock info missing from UI #11219
Closed
2 of 3 tasks
Labels
Comments
Hi, @mnarozny. Can I be assigned to this issue? I check the workflow you paste and so far I notice,
I want to fix this. It seems when job-1 is completed then job-2 should not run. as cache is hit. |
shmruin
added a commit
to shmruin/argo-workflows
that referenced
this issue
Jul 26, 2023
…argoproj#11219 Signed-off-by: shmruin <[email protected]>
shmruin
added a commit
to shmruin/argo-workflows
that referenced
this issue
Aug 2, 2023
…argoproj#11219 Signed-off-by: shmruin <[email protected]>
shmruin
added a commit
to shmruin/argo-workflows
that referenced
this issue
Aug 3, 2023
…argoproj#11219 Signed-off-by: shmruin <[email protected]>
juliev0
pushed a commit
that referenced
this issue
Aug 7, 2023
…#11219 (#11456) Signed-off-by: shmruin <[email protected]>
45 tasks
shmruin
added a commit
to shmruin/argo-workflows
that referenced
this issue
Aug 15, 2023
…argoproj#11219 (argoproj#11456) Signed-off-by: shmruin <[email protected]>
terrytangyuan
pushed a commit
that referenced
this issue
Aug 15, 2023
…#11219 (#11578) Signed-off-by: shmruin <[email protected]>
5 tasks
3 tasks
dpadhiar
pushed a commit
to dpadhiar/argo-workflows
that referenced
this issue
May 9, 2024
…argoproj#11219 (argoproj#11578) Signed-off-by: shmruin <[email protected]> Signed-off-by: Dillen Padhiar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
When using both memoize and mutex in a template, the cache check happens prior to the mutex check and the UI does not show any information about the job waiting for a lock to be released.
If I have a long running template and multiple workflows run it, I was expecting the other workflows to wait for the cached result behind the lock before even starting, it appears the behaviour is that all workflows will all check cache in parallel for a cache-hit: NO and then proceed to run consecutively. Both in the UI and CLI, the information about the job waiting for a lock is missing.
Example workflow simplified to include two jobs but the same issue happens when multiple workflows use the template.
Version
v3.4.8
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: