Skip to content

fix(bigtable): check remaining deadline on client-initiated retries in RetryingVRpc - #14796

Merged
igorbernstein2 merged 1 commit into
googleapis:mainfrom
igorbernstein2:b573788617-2
Oct 27, 2026
Merged

igorbernstein2 merged 1 commit into
googleapis:mainfrom
igorbernstein2:b573788617-2

Conversation

@igorbernstein2

Copy link
Copy Markdown
Contributor

Require remaining operation deadline (timeRemainingMs > 1) before scheduling client-initiated retries (UNCOMMITED or idempotent TRANSPORT_FAILURE) in RetryingVRpc.Active.shouldRetry.

@igorbernstein2
igorbernstein2 requested review from a team as code owners October 27, 2026 21:00

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the retry logic in RetryingVRpc to ensure that client-initiated retries respect the remaining deadline and are capped at three attempts. It also adds a corresponding unit test clientRetryRespectsDeadline to verify this behavior. There are no review comments, and I have no feedback to provide.

@igorbernstein2
igorbernstein2 merged commit a04e24c into googleapis:main Oct 27, 2026
205 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants