fix(CDC): fallback on transient proxy read errors#11626
Merged
tyler-french merged 1 commit intomasterfrom Mar 19, 2026
Merged
Conversation
d0c9672 to
a026537
Compare
a026537 to
26c8e79
Compare
vanja-p
approved these changes
Mar 19, 2026
26c8e79 to
9188491
Compare
tyler-french
added a commit
that referenced
this pull request
Mar 19, 2026
If we didn't read any frames, we should fall back from transient proxy issues from a remote read. We see some of these occuring: ``` chunk_local_read_error (DeadlineExceeded) chunk_local_read_error (Unavailable) ``` The client should retry these anyway, but having the read not fail and continue as expected is safer and less disruptive. The metrics ensure we don't have these issues build up.
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
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.
If we didn't read any frames, we should fall back from transient proxy issues from a remote read. We see some of these occuring:
The client should retry these anyway, but having the read not fail and continue as expected is safer and less disruptive. The metrics ensure we don't have these issues build up