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

Presumably a fix for deadlock (see #2041). #2042

Closed
wants to merge 1 commit into from

Conversation

vdbergh
Copy link
Contributor

@vdbergh vdbergh commented May 29, 2024

We use a separate lock to update aggregates. To this end we extend self.active_run_lock() with an optional argument name to be able to have different locks associated with the same run_id.

@vdbergh vdbergh mentioned this pull request May 29, 2024
We use a separate lock to update aggregates. To this end we
extend self.active_run_lock() with an optional argument
"name" to be able to have different locks associated with the same
run_id.
@vdbergh
Copy link
Contributor Author

vdbergh commented May 30, 2024

If #2029 would be merged then a better fix would be to do the scavenging of dead tasks as a separate scheduled task (as mentioned in #2029 (comment)). This does not need the run_cache_lock so the cycle would be broken in another way.

@vdbergh vdbergh marked this pull request as draft May 31, 2024 09:33
@vdbergh
Copy link
Contributor Author

vdbergh commented May 31, 2024

I have drafted this since #2029 is now being tested.

@vdbergh
Copy link
Contributor Author

vdbergh commented May 31, 2024

I am closing this now in view of the merging of #2029

@vdbergh vdbergh closed this May 31, 2024
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

Successfully merging this pull request may close these issues.

1 participant