[9.3.0] remote: add gRPC service config support by sluongng · Pull Request #30666 · bazelbuild/bazel

sluongng · 2026-08-11T11:22:09Z

Remote cache users currently have one --remote_timeout value that
applies across remote gRPC calls. That is a poor fit because fast
control-plane RPCs such as action cache lookups benefit from short
deadlines, while ByteStream reads and writes may need much longer
deadlines for large blobs. Setting the flag too low can make uploads or
downloads fail consistently; setting it too high makes stale requests
wait too long before Bazel retries.

This follows the direction discussed in
#26741.

This PR keeps the default user experience unchanged while moving remote
gRPC timeout handling onto service config, then adds an opt-in advanced
override.

It is structured as two commits:

remote: drive gRPC deadlines from service config generates the same
timeout policy Bazel previously applied from --remote_timeout,
installs it on remote gRPC channels, and removes per-stub deadline
plumbing.
remote: accept gRPC service config files adds
--remote_grpc_service_config for a user-owned JSON file. The initial
supported schema is intentionally restricted to methodConfig,
name, and timeout; unsupported fields such as retry, hedging,
load balancing, and health checking are rejected so Bazel can expand
support deliberately later.

Cherry-pick of #29912.

Remote cache users currently have one `--remote_timeout` value that applies across remote gRPC calls. That is a poor fit because fast control-plane RPCs such as action cache lookups benefit from short deadlines, while ByteStream reads and writes may need much longer deadlines for large blobs. Setting the flag too low can make uploads or downloads fail consistently; setting it too high makes stale requests wait too long before Bazel retries. This follows the direction discussed in bazelbuild#26741. This PR keeps the default user experience unchanged while moving remote gRPC timeout handling onto service config, then adds an opt-in advanced override. It is structured as two commits: - `remote: drive gRPC deadlines from service config` generates the same timeout policy Bazel previously applied from `--remote_timeout`, installs it on remote gRPC channels, and removes per-stub deadline plumbing. - `remote: accept gRPC service config files` adds `--remote_grpc_service_config` for a user-owned JSON file. The initial supported schema is intentionally restricted to `methodConfig`, `name`, and `timeout`; unsupported fields such as retry, hedging, load balancing, and health checking are rejected so Bazel can expand support deliberately later. Closes bazelbuild#29912. PiperOrigin-RevId: 952089183 Change-Id: I0101d0cafb9e7593a16c4106372d288c8ef0237c (cherry picked from commit 3510ade)

sluongng mentioned this pull request Aug 11, 2026

[9.3.0] remote: add gRPC download idle timeout #30667

Draft

sluongng force-pushed the sluongng/cherrypick-29912-9.3.0 branch from 086dae5 to 224e157 Compare August 11, 2026 12:46

sluongng marked this pull request as ready for review August 11, 2026 13:53

sluongng requested a review from a team as a code owner August 11, 2026 13:53

github-actions Bot added team-Core Skyframe, bazel query, BEP, options parsing, bazelrc team-Remote-Exec Issues and PRs for the Execution (Remote) team awaiting-review PR is awaiting review from an assigned reviewer labels Aug 11, 2026

sluongng mentioned this pull request Aug 11, 2026

[9.3.0] remote: add gRPC service config support #30411

Open

iancha1992 requested a review from coeuvre August 11, 2026 18:33

coeuvre approved these changes Aug 12, 2026

View reviewed changes

coeuvre added this pull request to the merge queue Aug 12, 2026