[8.8.0] Support bounded parallel chunk transfers - #29873
Merged
iancha1992 merged 1 commit intoJul 10, 2026
Merged
Conversation
sluongng
force-pushed
the
sluongng/cherry-pick-29341-8.8.0
branch
from
June 17, 2026 12:42
87d9fb7 to
1f31e78
Compare
sluongng
marked this pull request as ready for review
June 17, 2026 12:54
github-actions
Bot
added
team-Remote-Exec
iancha1992
enabled auto-merge
June 17, 2026 18:11
Member
|
@sluongng Could you please resolve the conflict? |
The 8.8.0 cherry-pick tracked by bazelbuild#29870 is needed because users enabling `--experimental_remote_cache_chunking` can still see large CDC blobs transfer chunks serially on this release branch. Backport bazelbuild#29341 so chunked uploads and downloads use a bounded per-blob sliding window while existing remote cache connection limits continue to bound global RPC concurrency. The 8.8.0 branch does not have the newer `GrpcCacheClient.shouldVerifyDownloads()` helper or the split remote Java BUILD targets. Wire whole-blob verification through `RemoteOptions.remoteVerifyDownloads` and keep the benchmark on this branch's coarse remote target layout. Refs bazelbuild#29870. PiperOrigin-RevId: 919144974 Change-Id: Iaa0ca8971bd21c879f21c708327b5ddd837ecf1f (cherry picked from commit 084958b)
auto-merge was automatically disabled
June 27, 2026 12:01
Head branch was pushed to by a user without write access
sluongng
force-pushed
the
sluongng/cherry-pick-29341-8.8.0
branch
from
June 27, 2026 12:01
1f31e78 to
de0efee
Compare
Contributor
Author
|
Merge conflict is resolved. I don't think the remaining CI failure is related to this PR: the only failing check is |
Contributor
Author
|
@iancha1992 do you need anything else from my end for this? |
Contributor
|
@tjgq would you be able to review this? Thanks! |
iancha1992
enabled auto-merge
June 29, 2026 18:32
tjgq
added
awaiting-PR-merge
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Jul 8, 2026
Contributor
Author
|
hmm should I rebase the branch or you can start the merge queue on your side @iancha1992 Im not familiar with the cherr-pick CI setup |
iancha1992
removed
the
awaiting-PR-merge
Contributor
|
@iancha1992 The build on the merge queue says it needs approval to proceed. |
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Jul 8, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Jul 9, 2026
Contributor
|
@iancha1992 It seems like someone needs to approve the CI build to start once its running in the merge queue. |
Member
@tyler-french Yes, we are aware and on it to fix this currently. |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 10, 2026
Merged
via the queue into
bazelbuild:release-8.8.0
with commit Jul 10, 2026
2cd0c53
46 checks passed
Contributor
Author
|
Wooo! Great job getting the merge queue fixed! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #29870.
This cherry-picks #29341 to release-8.8.0 because users enabling
--experimental_remote_cache_chunkingcan still see large CDC blobs transfer chunks serially on this release branch. The backport lets chunked uploads and downloads use a bounded per-blob sliding window while existing remote cache connection limits continue to bound global RPC concurrency.The 8.8.0 branch does not have the newer
GrpcCacheClient.shouldVerifyDownloads()helper or the split remote Java BUILD targets. This backport wires whole-blob verification throughRemoteOptions.remoteVerifyDownloadsand keeps the benchmark on this branch's coarse remote target layout.