Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GrpcRetryer now retries underlying DEADLINE_EXCEEDED if the root gRPC context deadline is not expired #709

Merged
merged 2 commits into from Sep 11, 2021

Conversation

Spikhalskiy
Copy link
Contributor

@Spikhalskiy Spikhalskiy commented Sep 11, 2021

What was changed

GrpcRetryer now retries underlying DEADLINE_EXCEEDED if the root gRPC context deadline is not expired

Why?

The behavior of GrpcRetryer has been changed in java-sdk#1.3.0 that causes potential regressions when GrpcRetryer is used with DeadlineGrpcInterceptor like described in #708

Closes #708

Comment on lines +460 to +461
Preconditions.checkArgument(
timeout.toMillis() > 70_000, "rpcLongPollTimeout has to be longer 70s");
Copy link
Member

Choose a reason for hiding this comment

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

Since we're already deprecating here I dunno that we need to potentially cause people pain by throwing here if they're already setting it too low.

I can go either way here though so if you want to keep it go for it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Setting less than 70s here now is just dangerous. So, I think it's the best we can do here.

…yer/GrpcRetryerUtils.java

Co-authored-by: Spencer Judge <sjudge@hey.com>
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.

Regression on GrpcRetryer + GrpcDeadlineInterceptor
3 participants