We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Deadlines guide states:
Deadline on the client (..) If a server has gone past the deadline when processing a request, the client will give up and fail the RPC with the DEADLINE_EXCEEDED status.
Deadline on the client
(..)
If a server has gone past the deadline when processing a request, the client will give up and fail the RPC with the DEADLINE_EXCEEDED status.
We don't currently do this (we rely on the server to respect grpc-timeout).
grpc-timeout
The timeout should apply even when wait-for-ready is enabled, see https://grpc.io/docs/guides/wait-for-ready/ .
The text was updated successfully, but these errors were encountered:
See also discussion of timeout_on_sleeping_server in interop.md; we might need to update that once this is fixed.
timeout_on_sleeping_server
interop.md
Sorry, something went wrong.
Implement client-side timeouts
6633a50
Closes #221.
8a6735d
ba7d442
edsko
No branches or pull requests
The Deadlines guide states:
We don't currently do this (we rely on the server to respect
grpc-timeout
).The timeout should apply even when wait-for-ready is enabled, see https://grpc.io/docs/guides/wait-for-ready/ .
The text was updated successfully, but these errors were encountered: