1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Could you please share the exact error with which the query fails?
based on the few information it could be that when the lambda function executes the query it submits more queries that your quota allow as explained here.
If this is the case you could be able to resolve the issue either:
- requesting a quota increase (could not work if later you continue to submit more queries than the quota)
- throttling the number of queries that your lambda can run in parallel.
- set up a retry mechanism hope this helps
Thanks, that was more or less the entire message, i had previously hit the quota exceeded messages, when this happens you get a meaningful error. I have asked for a quota increase but this particular message was not quota based (or the error was not saying quota), even when only one process was running I was getting random instances of these. That was on the 10th, however yesterday this behaviour stopped, the same processes running yesterday didn't fail randomly in the same way. My gut is something was failing behind the scenes and AWS have resolved the issue in this region. I did spend a day adding in retry mechanisms and reducing the batch sizes of the queries to make my process more tolerant to things like this.