Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

PickFirstLeafLoadBalancer may get stuck in Idle on backend address change

未关闭
#12,395 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
java

调研方向

从 core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java 开始,重点关注 resolver 更新、subchannel 移除、channel 状态、Idle picker,以及报告中关联的 ExitIdle 路径。根据所引用的 grpc-go 修复重现或跟踪事件序列,并检查现有的 PickFirstLeafLoadBalancer 测试(如果有)。完成的标准是:后端地址发生变化时,balancer 不能在未重新连接到新 endpoint 的情况下保持在 IDLE 状态。

由索引模型根据 Issue 内容生成。

描述

A bug was found in the new pickfirst balancer in gRPC Go which can cause the balancer to get stuck in IDLE state: https://github.com/grpc/grpc-go/pull/8615.

The implementation of the pickfirst LB in Java is similar, so it may suffer from the same issue. The order of events that lead to the bug is as follows:

  1. Existing connection breaks, the balancer requests re-resolution and reports IDLE. PF updates the channel state to IDLE with an Idle picker.
  2. An RPC is made, triggering the balancer to exit idle through the picker. The balancer attempts to re-connect the failed subchannel.
  3. The resolver produces a new endpoint list, removing the endpoint used by the existing subchannel. PF removes the existing subchannel. Since the balancer didn't update the channel state to CONNECTING yet, pickfirst thinks that it's still in IDLE and doesn't start connecting to the new endpoints.
  4. New RPC requests trigger the idle picker, but it's a no-op since it only triggers the balancer's ExitIdle method once.
主要语言
Java
星标
12.1k
派生
4k
平均合并
2 天 1 小时
30 天内合并 PR
31

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

grpc/grpc-java 的其他 Issue

查看 grpc/grpc-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。