LoadBalancer/Subchannel might need keep in TRANSIENT_FAILURE until READY
- 主要言語
- Java
- スター
- 12.1k
- フォーク
- 4k
- 平均マージ
- 2日 17時間
- マージ済み PR(30日)
- 37
説明
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.
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- java
- 領域
- distributed-systems, networking
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100