DEADLINE_EXCEEDED makes application not receiving messages at all
See original GitHub issueEnvironment details
Node.js version: v12.7.0 npm version: 6.10.0 @google-cloud/pubsub version: “^1.0.0”,
Error:
insertId: "gnr3q1fz7eerd" jsonPayload: { level: "error" message: "unhandledRejection" originalError: { ackIds: [1] code: 4 details: "Deadline exceeded" } }
After receiving this error, the app does not receive messages anymore and we have to exit the application to recreate the kubernetes pod.
Any help would be appreciated!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:12
- Comments:99 (29 by maintainers)
Top Results From Across the Web
Troubleshooting DEADLINE_EXCEEDED errors on ...
When accessing Cloud Spanner APIs, requests may fail due to “Deadline Exceeded” errors. This error indicates that a response has not been ...
Read more >gRPC DEADLINE_EXCEEDED even that the server is up ...
Do you set any deadline? ... you'll get DEADLINE_EXCEEDED X milliseconds after you opened a stream (not send or receive any messages!)
Read more >Handle Context Deadline Exceeded error in Go (Golang)
Setting timeouts on requests is a good practice in a production environment to ensure that you always get a response (or error) in...
Read more >Connectivity issues after upgrading to OpenShift Container ...
... Get "https://oauth-openshift.apps.openshift.example.com/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting ...
Read more >Fix problems sending, receiving or connecting to Messages
Learn how to change your default texting app. Make sure your carrier supports SMS, MMS, or RCS messaging. Check your plan or credit...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pwrkpop @npomfret @xoraingroup, rather than rolling back to
0.29.1
of@google-cloud/pubsub
I recommend one of the following workarounds:Using grpc, rather than @grpc/grpc-js
@google-cloud/pubsub
, add the dependencygrpc
(this is the old gRPC transport layer).☝️ this same approach can be used for other libraries that use gRPC, e.g.,
Using the workaround recommended by @Redgwell
We potentially have a reproduction of the issue described in this thread (thanks @Redgwell for pointing us in the right direction), and will hopefully have a fix out soon that makes either of these workaround unnecessary.
I can confirm this after upgrading to PubSub ^1.0.0, all our services stop sending pubsubs after the error occurs.
The full stacktrace is
Can I suggest raising the priority on this issue?