Closed scottgigante closed 1 week ago
I'm afraid that this looks like a nasty interaction between gevent
and boto3
.
https://github.com/boto/boto3/issues/3141
I don't think there's much can be done here.
You could experiment with not setting use_threads=True
. If that works, I'd be willing to take a PR that exposes this as a config setting.
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?
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 https://github.com/etianen/django-s3-storage/issues/162#issuecomment-2278086115, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABEKCCFSCMI6LRZT3CG47LZQTHF5AVCNFSM6AAAAABLKUIFKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGA4DMMJRGU . You are receiving this because you commented.Message ID: @.***>
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?