-
-
Notifications
You must be signed in to change notification settings - Fork 863
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
S3Boto3Storage still showing multithreading issues in 1.5.2 #268
Labels
Comments
2 tasks
tomkins
added a commit
to tomkins/django-storages
that referenced
this issue
Jul 7, 2017
Documentation for boto3 recommends a session per thread - https://boto3.readthedocs.io/en/latest/guide/resources.html#multithreading-multiprocessing As the storage class is (usually) only instantiated once per process, we need to set a thread local for each thread/connection used. Fixes jschneier#268
jschneier
pushed a commit
that referenced
this issue
Jul 27, 2017
Documentation for boto3 recommends a session per thread - https://boto3.readthedocs.io/en/latest/guide/resources.html#multithreading-multiprocessing As the storage class is (usually) only instantiated once per process, we need to set a thread local for each thread/connection used. Fixes #268
jschneier
added a commit
that referenced
this issue
Jul 27, 2017
This was referenced Jul 27, 2017
This was referenced Jul 31, 2017
This was referenced Aug 21, 2017
This was referenced Oct 2, 2017
This was referenced Nov 10, 2017
nitely
pushed a commit
to satellogic/django-storages
that referenced
this issue
Jul 30, 2018
Documentation for boto3 recommends a session per thread - https://boto3.readthedocs.io/en/latest/guide/resources.html#multithreading-multiprocessing As the storage class is (usually) only instantiated once per process, we need to set a thread local for each thread/connection used. Fixes jschneier#268
nitely
pushed a commit
to satellogic/django-storages
that referenced
this issue
Jul 30, 2018
nitely
pushed a commit
to satellogic/django-storages
that referenced
this issue
Jul 30, 2018
Documentation for boto3 recommends a session per thread - https://boto3.readthedocs.io/en/latest/guide/resources.html#multithreading-multiprocessing As the storage class is (usually) only instantiated once per process, we need to set a thread local for each thread/connection used. Fixes jschneier#268
nitely
pushed a commit
to satellogic/django-storages
that referenced
this issue
Jul 30, 2018
nitely
pushed a commit
to satellogic/django-storages
that referenced
this issue
Jul 30, 2018
Documentation for boto3 recommends a session per thread - https://boto3.readthedocs.io/en/latest/guide/resources.html#multithreading-multiprocessing As the storage class is (usually) only instantiated once per process, we need to set a thread local for each thread/connection used. Fixes jschneier#268
nitely
pushed a commit
to satellogic/django-storages
that referenced
this issue
Jul 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using
S3Boto3Storage
in 1.5.2 with uWSGI & 8 threads, and my workers are exiting like so:Unfortunately I'm not getting a stacktrace. I saw the bug fix that went into 1.5.2 in the release notes (#238) and, on a whim, switched to 1 thread per worker, and the segfaults went away. I also tried
S3BotoStorage
with multiple threads, and it works fine.Happy to help debug this if I can, but I'm not entirely sure where to start.
The text was updated successfully, but these errors were encountered: