-
Notifications
You must be signed in to change notification settings - Fork 94
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
Frequent time-outs / failures in storage.save
used with gevent
#162
Comments
I'm afraid that this looks like a nasty interaction between I don't think there's much can be done here. You could experiment with not setting |
Ah you're a lifesaver!! Thank you. This solved my issue. Turns out you already expose it as |
A short comment on the README next to the setting would be a good idea.
Happy to take that PR.
…On Fri, 9 Aug 2024 at 15:32, Scott Gigante ***@***.***> wrote:
Ah you're a lifesaver!! Thank you. This solved my issue. Turns out you
already expose it as AWS_S3_USE_THREADS, and setting that to False in
settings.py resolved the timeouts. Would it be worth adding a comment to
the README on this? Or is the existence of this issue sufficient?
—
Reply to this email directly, view it on GitHub
<#162 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABEKCCFSCMI6LRZT3CG47LZQTHF5AVCNFSM6AAAAABLKUIFKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGA4DMMJRGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
storage.save
storage.save
used with gevent
I'm using django-health-check with django-s3-storage and getting frequent (like, once every few hours) failures. This may be related to my threading setup (I'm using gevent) but it's causing my container to frequently fail health checks. This began when I set AWS_S3_CONNECT_TIMEOUT in my settings.py, but previously I had unexplained timeouts instead of exceptions on the healthcheck, so I suspect it's the same issue with and without the connect timeout.
I know this is hard to repro, but any ideas?
The text was updated successfully, but these errors were encountered: