LoadBalancer/Subchannel might need keep in TRANSIENT_FAILURE until READY
- Lenguaje dominante
- Java
- Estrellas
- 12.1k
- Forks
- 4k
- Merge medio
- 2 d 17 h
- PR fusionados (30 d)
- 37
Descripción
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.
Guía de contribución
Línea de trabajo
Start by reading issue #6650 and locating round-robin (RR) handling for general load balancers and subchannels. Trace how TRANSIENT_FAILURE and CONNECTING are represented, then identify the relevant existing tests. Done means unavailable subchannels remain considered TRANSIENT_FAILURE until READY, while new and recently-READY subchannels can still connect.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- distributed-systems, networking
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100