2 Answers
- Newest
- Most votes
- Most comments
0
I think it is related to throttling issue.
If your queries exceed the limits of dependent services such as Amazon S3, AWS KMS, AWS Glue, or AWS Lambda, the following messages can be expected. To resolve these issues, reduce the number of concurrent calls that originate from the same account.
https://docs.aws.amazon.com/athena/latest/ug/performance-tuning-s3-throttling.html
answered 7 months ago
0
AWS sort of had a meltdown (at least in my region) a few days ago, and these kinds of errors were common. Since then, the errors come less frequently, but I'm still seeing them. There are some other queries that used to run reliably that "exhaust resources" every time now. I wonder if Amazon implemented some emergency throttling when the meltdown occurred.
answered 7 months ago
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 months ago