[release/6.0] Handle ERROR_CONNECTION_INVALID after ERROR_MORE_DATA #36147
Conversation
This file contains hidden or 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
github-actions
bot
requested review from
BrennanConroy,
Tratcher and
halter73
as code owners
ghost
added
the
Tratcher
approved these changes
Sep 3, 2021
Member
|
@wtgodbe merge please? |
amcasey
added
area-networking
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.
Backport of #36146 to release/6.0
/cc @Tratcher
This handles a disconnect race condition more gracefully.
Customer Impact
Before, ERROR_CONNECTION_INVALID was not expected so it would be logged as an Error and trigger investigations. Now it's automatically handled.
Testing
Manual
Risk
Low