Problem you have encountered:
After turning exactly once delivery in high traffic subscriptions, sudenly I get these errors:
“io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Some acknowledgement ids in the request were invalid. This could be because the acknowledgement ids have expired or the acknowledgement ids were malformed”.
And the subscription’s amount of messages immediately shoot up, after turning this off again, the problem is resolved.
Could this be related to the quotas ?
What you expected to happen:
The subscription currently has 600s of ack deadline set in GCP. No message is actually taking more than that to be processed.
Steps to reproduce:
Turn on exactly once delivery in subscriptions that receive relatively a lot of messages.
Ordered delivery IS NOT enabled.
Other information (workarounds you have tried, documentation consulted, etc):
From the docs that Ive found none states that any change is done to the ack deadline.
From this topic previously open on issue tracker ive got the response:
”
Status: Won’t Fix (Infeasible)
Hello (PII Removed by Staff),
Thank you for reaching out to us!
This specific error is usually not a direct quota exceeded error which would typically return RESOURCE_EXHAUSTED. This error is a by-design behavior of the Exactly-Once Delivery (EOD) feature in Google Cloud Pub/Sub. When EOD is enabled, Pub/Sub uses a persistence layer to track message states with versioned acknowledgement IDs.
Also, this issue is outside the scope of the Issue Tracker, which is for reporting bugs and requesting features on Google Cloud products. You can learn more here.
For technical questions, I recommend posting on Google Cloud Data Analytics Community Forum. I’ll now close this thread, as it will no longer be monitored. Feel free to create a new issue if needed.
**Google Cloud Platform
”
**
So here am i, the main issue i see here is:
- why does my apps logs this all of a sudden and acks seems to fail as my subscription unacked messages shoot up ?
- Why turning it off immediately fixes the problem ? - I was using an ack DL of 10mins, doesnt activating this feature automatically changes my sub ack deadline some how ? that is my assumption