- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi Charles, the particular limit you're hitting is an internal limit that's currently not listed in the public documentation. Could you open a case using this link or file a limit increase on DeleteFaces API and we can then engage on the case to help.
We understand that the limit is not a good customer experience and there're a few options that's available to help.
Hi!
The 2 pages I'm looking at are https://docs.aws.amazon.com/rekognition/latest/dg/limits.html and https://docs.aws.amazon.com/general/latest/gr/rekognition.html.
I don't see anything else. Could you check https://us-west-2.console.aws.amazon.com/servicequotas/home/services/rekognition/quotas/L-220834FB (Use the region you're working in) and see the history?
Some options include configuring exponential backoff and jitter, configuring retries, queuing as well. Alternatively, you could increase the service quota too.
The page shows a <5% usage of the deletefaces. I just retried, and I managed to get one batch of 4096 faces deleted, but the second batch (5s pause between) of 4096 failed with the provisioned rate limit error. I went into cloudwatch so I can see the exact metrics for the deleteface api, and I can see exactly two calls in the last hour, one successful, one throttled. I am using Ireland but I believe the limit is 5 calls/s everywhere. I am clearly not hitting that limit. I wonder if it has something to do with the size of the collection (>500k), but that is well within the 20m limit.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
Thanks. I have already requested a limit increase (thinking I was somehow hitting the 5 calls/s.) I will mention your comment. If it is not confidential, I would be curious to know what that internal limit consists in, just so I can code to stay clear of it.