-
Notifications
You must be signed in to change notification settings - Fork 1.5k
pubsub: No errors exposed for resource exhausted errors #1166
Copy link
Copy link
Closed
Labels
api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Description
Client
PubSub (latest master: )
Describe Your Environment
CentOS 7 on GCE
Expected Behavior
I expect an error from Receive if there is a resource exhaustion on StreamingPull requests.
Actual Behavior
Receive doesn't return an error and I assume silently retries.
We apparently hit our concurrent StreamingPull limit (120) months ago and never knew because Receive never returned an error. When we spun up more servers today they were only receiving 1/10th the amount of messages the other servers were and we couldn't figure out why until we happened to notice the Pub/Sub API dashboard showed 99.96% of StreamingPull calls errored.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
api: pubsubIssues related to the Pub/Sub API.Issues related to the Pub/Sub API.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.