grpclb: LoadBalancer.requestConnection() may be ignored if it's called before subchannels are created
- Langage dominant
- Java
- Étoiles
- 12.1k
- Forks
- 4k
- Merge moyen
- 2 j 17 h
- PR mergées (30 j)
- 37
Description
### What version of gRPC-Java are you using?
v1.32.1
### What did you expect to see?
Calling `ManagedChannel.getState(true)` will make the channel to try to connect to the server at least once, no matter when it's called.
### What did you see instead?
Calling `ManagedChannel.getState(true)` makes the channel try to connect to server only if it's called after subchannels are created, i.e., after name resolution in pick-first, and after backend addresses are received in grpclb. If `getState(true)` is called before that point, the channel won't try to connect to servers after subchannels are created, unless `getState(true)` is called again.
/cc @ejona86
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start with ManagedChannel.getState(true) and LoadBalancer.requestConnection(), then compare the pick-first and grpclb timing described in the report. Reproduce a call made before subchannels are created; the fix is complete when that call still causes a server connection after subchannels become available.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- grpc, java
- Domaine
- api, networking
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100