runtime: fix flakey connector deadlock #1188
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Testing:
|
travjenkins
approved these changes
Sep 15, 2023
Image connectors can deadlock at high volumes of requests and response due to channel stuffing. Specifically it's not okay to await a send into the container while not concurrently polling for container responses. Re-work the state machine to forward non-error responses using a separate spawned task, which is joined over only upon terminal error or completion.
jgraettinger
force-pushed
the
johnny/connector-deadlock
branch
from
c704370
to
2d3a0ff
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Image connectors can deadlock at high volumes of requests and response due to channel stuffing. Specifically it's not okay to await a send into the container while not concurrently polling for container responses.
Re-work the state machine to forward non-error responses using a separate spawned task, which is joined over only upon terminal error or completion.
Description:
(Describe the high level scope of new or changed features)
Workflow steps:
(How does one use this feature, and how has it changed)
Documentation links affected:
(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)
Notes for reviewers:
(anything that might help someone review this PR)
This change is