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

LoadBalancer/Subchannel might need keep in TRANSIENT_FAILURE until READY #6906

Open
dapengzhang0 opened this issue Apr 7, 2020 · 1 comment
Milestone

Comments

@dapengzhang0
Copy link
Member

This is the same issue as #6650 for general lb/subchannel.

If you have enough backends and they are all unavailable, then it becomes likely that at least one of them will be CONNECTING. That will delay RPCs and avoid giving them a clear error message.
When a subchannel becomes TRANSIENT_FAILURE, we want RR to continue considering it (for channel state and picking logic) TRANSIENT_FAILURE until the subchannel becomes READY. That means it would "ignore" CONNECTING subchannels, except for new and recently-READY subchannels.

@ejona86
Copy link
Member

ejona86 commented Apr 7, 2020

This needs cross-language agreement, and that will need a redesign of pick first. There is nothing currently to be done for this issue.

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

No branches or pull requests

2 participants