#20562: Docs: How to use django ORM with multiprocessing
--------------------------------------+------------------------------------
Reporter: Thomas Güttler | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.5
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Antony V. Badaykin):
Replying to [comment:8 Aymeric Augustin]:
> Most users of the Django ORM use it from multiple processes, since most
production WSGI servers use multiple processes :-)
>
> This question isn't specific to Django. The general problem that you
can't carry sockets across fork.
>
> If your Django process has network connections to remote data stores and
you want to fork, you need to close these connections before forking.
(Usually, they're reopened automatically on the next access.)
>
> In practice, applications servers fork before Django does anything, **so
this issue only arises when you fork in a management command**, typically
because you're trying to use `multiprocessing`.
What about to add some top-level wrapper, like `MultiprocessingCommand`
for example, that's carry out about connections and etc?
--
Ticket URL: <https://code.djangoproject.com/ticket/20562#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.807079efd4b538cb51322fdd15731701%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
