This repository was archived by the owner on Mar 19, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
should deadlines apply to streaming rpcs? #482
Description
I'm not sure if this is intended or not (it very well might be) but when a deadline is set for a streaming rpc the stream shuts down with a Deadline Exceeded error regardless of whether or not a connection is made once the deadline is hit.
I think this might be leading to strange behavior where the deadline must be increased by a great margin in order to allow the stream to stay open for longer. However this can be a problem in the event of an actual timeout, potentially causing client code to hang longer than necessary.
I think this is a gax issue because it applies default deadlines for streaming rpcs with no way to opt out, however this might also be a grpc issue? I'm not really sure, but I figured I'd start here!
Activity
vchudnov-g commentedon Nov 10, 2018
@alexander-fenster Any updates?
alexander-fenster commentedon Nov 12, 2018
@callmehiphop This was lost in the list of issues for a long time :)
For proper triaging: do you have any ongoing problems with the deadlines being applied to streaming methods in any of the libraries you support?
callmehiphop commentedon Nov 15, 2018
@alexander-fenster currently no, however we could definitely simplify code in the PubSub client if this were behaving as expected.
alexander-fenster commentedon Jul 21, 2022
Closing for now, please reopen if this functionality is needed by someone.
Update kokoro config (#482)
fix(deps): update dependency uuid to v9 (#482)
Update kokoro config (#482)
fix(deps): update dependency uuid to v9 (#482)
Update kokoro config (googleapis#482)