Ack fails, with "Failed to acknowledge" or Failed to "modifyAckDeadline"
See original GitHub issueThanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you’ve tried the usual “quick fixes”:
- Search the issues already opened: https://github.com/googleapis/nodejs-pubsub/issues
- Search the issues on our “catch-all” repository: https://github.com/googleapis/google-cloud-node
- Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
If you are still having issues, please be sure to include as much information as possible:
Environment details
- OS: Ubuntu 18.04
- Node.js version: 11.15
- npm version: 6.11.2
@google-cloud/pubsub
version: 32.0
Steps to reproduce
- Use version 0.31 or 0.32
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
80 % of messages fails to ack. Going back to version 0.22.2 the Ack errors disappears.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Method: projects.subscriptions.modifyAckDeadline
Modifies the ack deadline for a specific message. This method is useful to indicate that more time is needed to process a message...
Read more >Modify ack deadline in asynchronous subscriber
To get an idea why I'm trying to it: What I want to achieve is a kind of retry mechanism where messages that...
Read more >subscriptions() - Google Developers
Acknowledging a message more than once will not result in an error. ... To override this value for a given message, call #...
Read more >How to use modifyAckDeadline method in com.google.cloud ...
modifyAckDeadline (subscription, ackIds, ackDeadlineSeconds); Assert.fail("No exception raised"); } catch (InvalidArgumentException e) { // Expected ...
Read more >pubsub - Go Packages
Unless a message is acknowledged within the ack deadline, or the client requests that ... Context, id string, cfg SubscriptionConfig) (*Subscription, error) ...
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
No, native Node with project reference. As errors disappeared after deploying to the cloud, I think you can close this, and keep it as a reference that something is different (probably some network thing) between 0.22 and 1.0.
Regards Gunnar
@gberth thanks! You might try increasing the request timeout for acks/modacks. You can do it like so
It might also be worth noting that other users have reported similar issues when they create a lot of Subscription objects. The gRPC channel can only handle so many concurrent streams, so if you do have a lot of Subscription objects, I might suggest trying to either cache and re-use them where possible OR lower the number of streams created per Subscription object.