- Newest
- Most votes
- Most comments
Hi,
Can you check the AWS Service Quota for "Max concurrent job runs per account"? It might be 0 right now as there is an issue ongoing with several accounts were this limit sets to 0. And this then prevents any job from running
https://console.aws.amazon.com/servicequotas/home/services/glue/quotas (make sure it is the correct region)
Please, check if somehow you are not exceeding some service quota for Glue. See that Max jobs per trigger is 50. You mentioned 47 jobs, which is really close and potentially your code could maybe is trying to trigger more than once? Just a guessing, without access to code to take a look.
Some of them are soft limits that you can ask for an increase. If you believe there's some potential issue, please open a ticket to get support.
For my situation the solution in first comment fitted, Thanks for kindly answer.
I'm getting the same issue, all of the glue jobs that used to run normally before failed to run today. Max concurrent job runs per account is 0, also Max task dpus per account is 0, what happend?
AWS had an issue affecting multiple accounts. Sadly this was not visible on any status page. We only learned about it because the limit did set to 0 for us and kept on being set to 0 every two hours after we requested the limit increase (and got an auto accept)
Relevant content
- asked a year ago
AWS OFFICIALUpdated 2 months ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
For my situation this solution is work, Thanks!
In additional, you should checkout the quotas that should not be equal 0 e.g. max task dpus per account, and then request AWS support to set it back to defualt value, the problem should be resolved.