[java-storage] Feature request: expose ChannelPoolSettings on GrpcStorageOptions.Builder

未关闭
  • 哪里不对？
#14,519 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Dhriti07 已经在做这个了。

开始于 2026年9月29日。

  • #3556 来自 @DeepikaMamidipelly009 —— 已关闭，未合并

评估

难度
3/5
预计耗时
1-2 天
新手友好度
76/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
grpc, java
领域
api, backend, cloud

调研方向

Start in GrpcStorageOptions.Builder and follow resolveSettingsAndOpts() to see how InstantiatingGrpcChannelProvider is configured. Add the ChannelPoolSettings builder option, wire it through while preserving the unset default, and verify that the high-level Storage API exposes the configured pool settings.

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

描述

api: storage

Is your feature request related to a problem? Please describe.

We use StorageOptions.grpc() with Direct Path on GKE for high-throughput writes (WriteChannel, resumable uploads). A single commit can trigger hundreds of concurrent uploads per pod.

GrpcStorageOptions builds InstantiatingGrpcChannelProvider without setChannelPoolSettings(), so the default is effectively one gRPC channel. With ~100+ concurrent RPCs, calls queue on that channel and we see high tail latency and underused bandwidth.

ChannelPoolSettings can be set on StorageSettings + StorageClient, but the high-level Storage API from StorageOptions.grpc().build().getService() offers no way to pass those settings.

(google-cloud-storage 2.34.0+, resolves to 2.55.x in our build.)

Describe the solution you'd like

Add setChannelPoolSettings(ChannelPoolSettings) to GrpcStorageOptions.Builder, wired through to InstantiatingGrpcChannelProvider in resolveSettingsAndOpts(). Default unchanged when unset.

Storage storage = StorageOptions.grpc()
    .setProjectId(projectId)
    .setChannelPoolSettings(ChannelPoolSettings.builder()
        .setInitialChannelCount(8)
        .setMaxChannelCount(16)
        .setMaxRpcsPerChannel(50)
        .build())
    .build()
    .getService();

Describe alternatives you've considered

  • StorageClient + custom StorageSettings — channel pool works, but not compatible with high-level Storage / WriteChannel.
  • Copy resolveSettingsAndOpts() in app code — fragile.
  • Upload concurrency limit in app — does not fix single-channel RPC queuing.
主要语言
Java
星标
2.1k
派生
1.2k
平均合并
2 天 14 小时
30 天内合并 PR
192

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

googleapis/google-cloud-java 的其他 Issue

查看 googleapis/google-cloud-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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