Glue: Testing connection triggers "Task allocated capacity exceeded limit" error

0

We have a Glue connection that was running successfully. Now, though, even when testing the connection we get a "Task allocated capacity exceeded limit" error. We have checked the max DPUs and concurrency quotas. They're fine. The connection is going though a VPC, but that was working a couple of days ago. No CloudWatch logs are being written, so it's impossible to know what service / quota limit is triggering the error.

gefragt vor 2 Jahren358 Aufrufe
1 Antwort
0

I'll answer my own question :)

For some reason, AWS kept resetting my DPU quota to 0 after increasing it to 1000. So I just requested more than 1000 and now it's sticking.

beantwortet vor 2 Jahren

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen