8000 Deadlock when max action concurrency is reached · Issue #99 · proxystore/academy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Deadlock when max action concurrency is reached #99

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.

Sign up for GitHub

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

Jump to bottom
Open
gpauloski opened this issue May 12, 2025 · 0 comments
Open

Deadlock when max action concurrency is reached #99

gpauloski opened this issue May 12, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@gpauloski
Copy link
Contributor

It's possible to get a deadlock if the action thread pool of an agent gets filled up with actions that are blocking, causing no other actions to get scheduled. We've already started to document that agents have a max concurrency, but maybe we need a mechanism to warn the user when that happens?

I'm not 100% sure what the best approach is. We could default to no max concurrency, support and encourage async actions, or return errors to actions when the current thread pool is overloaded.
@gpauloski gpauloski added the bug Something isn't working label May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gpauloski
0