grpc: ensure transports are closed when the channel enters IDLE #6620
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.
Prior to channel idleness, sub-channels would be closed either because:
cc.ctx
is canceledIn the case of the channel moving to IDLE though, we were calling
ac.tearDown
, but this was not actually closing the transport because the passed in error was noterrConnDrain
.With this PR, we will always close the underlying transport from
ac.tearDown
, either gracefully or forcefully.RELEASE NOTES: