upstream: flb_upstream_conn busy flag addition #4125
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
Signed-off-by: Leonardo Alminana <[email protected]>
edsiper
added
backport to v1.8.x
Closed
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.
This PR is the replacement of PR #4124 which injected the busy flag state changes at the wrong places without taking TLS in consideration which was pointed out by krispraws, it was recreated instead of making another commit to keep the commit log tidier.
This is the original PR message :
This PR addresses what was discussed in PR #4107 as a simple way to delay the disposal of flb_upstream_conn instances before the coroutine is done using it.
Signed-off-by: Leonardo Alminana [email protected]