Skip to content
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.

Sign up for GitHub

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

Jump to bottom

client/SubConn: do not recreate addrConn if UpdateAddresses is called with the same addresses #5373

Merged
merged 5 commits into from
May 20, 2022
Merged

client/SubConn: do not recreate addrConn if UpdateAddresses is called with the same addresses #5373

merged 5 commits into from
May 20, 2022

Conversation

menghanl
Copy link
Contributor

Even if the SubConn is Connecting (there's no curAddr).

RELEASE NOTES:

  • client/SubConn: do not recreate addrConn if UpdateAddresses is called with the same addresses

@menghanl menghanl requested a review from dfawley May 20, 2022 00:17
@menghanl menghanl added this to the 1.47 Release milestone May 20, 2022
@dfawley dfawley assigned menghanl and unassigned dfawley May 20, 2022
@menghanl menghanl merged commit 30b9d59 into grpc:master May 20, 2022
@menghanl menghanl deleted the pickfirst_check_addrs branch May 20, 2022 22:17
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@dfawley dfawley dfawley approved these changes

Assignees

@menghanl menghanl

Labels
Type: Bug
Projects
None yet
Milestone
1.47 Release
Development

Successfully merging this pull request may close these issues.
2 participants
@menghanl @dfawley