Skip to content

Commit

Permalink
Removes out of date documentation for CELERYD_FORCE_EXECV (Issue #2020)
Browse files Browse the repository at this point in the history
  • Loading branch information
ask committed Nov 11, 2014
1 parent 3e91891 commit faf8795
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 18 deletions.
18 changes: 0 additions & 18 deletions docs/configuration.rst
Expand Up @@ -1361,24 +1361,6 @@ to have different import categories.
The modules in this setting are imported after the modules in
:setting:`CELERY_IMPORTS`.

.. setting:: CELERYD_FORCE_EXECV

CELERYD_FORCE_EXECV
~~~~~~~~~~~~~~~~~~~

On Unix the prefork pool will fork, so that child processes
start with the same memory as the parent process.

This can cause problems as there is a known deadlock condition
with pthread locking primitives when `fork()` is combined with threads.

You should enable this setting if you are experiencing hangs (deadlocks),
especially in combination with time limits or having a max tasks per child limit.

This option will be enabled by default in a later version.

This is not a problem on Windows, as it does not have `fork()`.

.. setting:: CELERYD_WORKER_LOST_WAIT

CELERYD_WORKER_LOST_WAIT
Expand Down
1 change: 1 addition & 0 deletions extra/release/verify_config_reference.py
Expand Up @@ -18,6 +18,7 @@
'CELERY_REDIS_PORT',
'CELERY_REDIS_DB',
'CELERY_REDIS_PASSWORD',
'CELERYD_FORCE_EXECV',
}


Expand Down

0 comments on commit faf8795

Please sign in to comment.