Browse Source

Removes out of date documentation for CELERYD_FORCE_EXECV (Issue #2020)

Ask Solem 10 years ago
parent
commit
faf8795a27
2 changed files with 1 additions and 18 deletions
  1. 0 18
      docs/configuration.rst
  2. 1 0
      extra/release/verify_config_reference.py

+ 0 - 18
docs/configuration.rst

@@ -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

+ 1 - 0
extra/release/verify_config_reference.py

@@ -18,6 +18,7 @@ ignore = {
     'CELERY_REDIS_PORT',
     'CELERY_REDIS_DB',
     'CELERY_REDIS_PASSWORD',
+    'CELERYD_FORCE_EXECV',
 }