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

Ensure that standby forwarding respects request timeouts #11322

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

ncabatoff
Copy link
Collaborator

When a standby does a ForwardRequest, it's not using the request context, and thus not getting timed out properly when it takes too long.

The rpcClientConnContext is still used to terminate gRPC internal/dialer-related goroutines, but the actual RPC is now timed out when the request times out, e.g. due to the default max request duration. This mirrors what we do with the parallel forwarding code in ENT.

…ext, and thus not getting timed out properly when it takes too long.

The rpcClientConnContext is still used to terminate gRPC internal/dialer-related goroutines, but the actual RPC is now timed out when the request times out, e.g. due to the default max request duration.  This mirrors what we do with the parallel forwarding code in ENT.
@ncabatoff ncabatoff requested a review from a team April 8, 2021 13:41
@ncabatoff ncabatoff added this to the 1.6.4 milestone Apr 8, 2021
@ncabatoff ncabatoff merged commit ad169e2 into master Apr 15, 2021
@ncabatoff ncabatoff deleted the make-forward-use-request-timeout branch April 15, 2021 14:23
ncabatoff added a commit that referenced this pull request Apr 15, 2021
…ext, and thus not getting timed out properly when it takes too long. (#11322)

The rpcClientConnContext is still used to terminate gRPC internal/dialer-related goroutines, but the actual RPC is now timed out when the request times out, e.g. due to the default max request duration.  This mirrors what we do with the parallel forwarding code in ENT.
@ncabatoff ncabatoff modified the milestones: 1.6.4, 1.7.1 Apr 15, 2021
ncabatoff added a commit that referenced this pull request Apr 16, 2021
#11362)

* When a standby does a ForwardRequest, it's not using the request context, and thus not getting timed out properly when it takes too long. (#11322)

The rpcClientConnContext is still used to terminate gRPC internal/dialer-related goroutines, but the actual RPC is now timed out when the request times out, e.g. due to the default max request duration.  This mirrors what we do with the parallel forwarding code in ENT.
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