Skip to content

caller_runs execution should not block the work queue #939

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

Merged
merged 2 commits into from
Mar 15, 2022

Conversation

chrisseaton
Copy link
Member

caller_runs execution was being done while the executor lock was held. This caused the entire executor’s work queue to be blocked, with worker threads not able to take new work. We’ve restructured so that the execution is done as deferred work, outside of the lock.

Fixes #933.

@chrisseaton chrisseaton requested a review from eregon March 13, 2022 15:22
@chrisseaton
Copy link
Member Author

Ignore the JRuby failures - they're unrelated. Fixing on another PR.

Copy link
Collaborator

@eregon eregon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just 1 comment

caller_runs execution was being done while the executor lock was held.
This caused the entire executor’s work queue to be blocked, with worker
threads not able to take new work. We’ve restructured so that the
execution is done as deferred work, outside of the lock.
@chrisseaton chrisseaton force-pushed the caller-runs-blocking branch from a5522c2 to b02930e Compare March 14, 2022 23:54
@chrisseaton
Copy link
Member Author

Please re-review @eregon.

@eregon eregon merged commit 858eaa5 into master Mar 15, 2022
@eregon eregon deleted the caller-runs-blocking branch March 15, 2022 12:36
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.

Worker threads get stuck when using caller_runs policy
2 participants