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.

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

core: ManagedChannelImpl to always use RetryingNameResolver (1.54.x backport) #10330

Merged
merged 1 commit into from
Jun 29, 2023

Conversation

temawi
Copy link
Contributor

@temawi temawi commented Jun 29, 2023

Backport of #10328

ManagedChannelImpl did not make sure to use a RetryingNameResolver if authority was not overriden. This was not a problem for DNS name resolution as the DNS name resolver factory explicitly returns a RetryingNameResolver. For polling name resolvers that do not do this in their factories (like the grpclb name resolver) this meant not having retry at all.

b/289123469

ManagedCahnnelImpl did not make sure to use a RetryingNameResolver if
authority was not overriden. This was not a problem for DNS name
resolution as the DNS name resolver factory explicitly returns a
RetryingNameResolver. For polling name resolvers that do not do this in
their factories (like the grpclb name resolver) this meant not having retry
at all.
@temawi temawi requested a review from ejona86 June 29, 2023 20:53
@temawi temawi merged commit a650c6f into grpc:v1.54.x Jun 29, 2023
@temawi temawi deleted the backport-fix-nr-retry-1.54 branch June 29, 2023 21:18
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants