-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.io.IOException in loading images #342
Comments
It has happened for questaGame as well.
|
Need a little more information I think to action this. |
HTTP 503 was being hit too often, so because we couldn't get in contact with you, we temporarily removed nginx rate limiting from We don't want biocache-store to become an issue that stops people accessing images.ala.org.au but the only way we could achieve the iNaturalist image loads which are a critical priority and not drop images from our nightly loads (also a critical priority) was to remove the nginx rate limiter. |
Thanks @ansell Currently seeing this when i try to load iNat
|
Mahmoud has enabled the daily iNaturalist API load, which is run using http:https://localhost:9193/job/iNaturalist%20Daily/ The result you are seeing is expected, as that particular delta load file has already been loaded. I have reenabled the nginx rate limiting on aws-image-service to enable replication of the issue, at the risk of images not consistently loading in tonight's regular data loads. |
Ive added some rate limiting logic and while it seems to running ok, Im unsure if it is sufficient without reliable replication of the issues. Still assessing if it has enough impact. The config property is
which defaults to 10 requests per second. Note the nginx configuration is currently set to
which is approximately 16 request a second. |
It's fixed since the snapshot version |
Loading sightings dr364 resulted in :
This happens when the image-service is flooded with lots of requests and cannot handle the load or rejected by nginx throttle mechanism. Lifting the throttling threshold didn't solve the issue. Need
try catch retry
mechanism (with a pause) or some sort of throttling on biocache-store side.The text was updated successfully, but these errors were encountered: