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

Default service config not honored if initial name resolution fails #11040

Open
temawi opened this issue Mar 26, 2024 · 1 comment
Open

Default service config not honored if initial name resolution fails #11040

temawi opened this issue Mar 26, 2024 · 1 comment
Labels
Milestone

Comments

@temawi
Copy link
Contributor

temawi commented Mar 26, 2024

If the name resolution fails we are supposed to rely on the default service config since there is no way to get one via name resolution. This currently only happens if there has been at least one successful name resolution call. If the first name resolution fails, ManagedChannelImpl does not apply the service config.

@sergiitk
Copy link
Member

sergiitk commented Mar 27, 2024

Came out of #11018. May be full or partial solution for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants