diff options
author | Graham Dumpleton <Graham.Dumpleton@gmail.com> | 2021-08-03 14:43:13 +1000 |
---|---|---|
committer | Graham Dumpleton <Graham.Dumpleton@gmail.com> | 2021-08-03 14:43:13 +1000 |
commit | cc813deaaa045417d01ada8f3eb317412a726635 (patch) | |
tree | e5da7f83995602c03c0f6f4766dc1f269280111e /docs | |
parent | 550bf8a7ab4914d11650627c4241076e8e2b2710 (diff) | |
download | mod_wsgi-cc813deaaa045417d01ada8f3eb317412a726635.tar.gz |
Set default for graceful timeout.
Diffstat (limited to 'docs')
-rw-r--r-- | docs/release-notes/version-4.9.0.rst | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/release-notes/version-4.9.0.rst b/docs/release-notes/version-4.9.0.rst index 67a9d48..36815a7 100644 --- a/docs/release-notes/version-4.9.0.rst +++ b/docs/release-notes/version-4.9.0.rst @@ -41,3 +41,18 @@ Features Changed for you, the value of ``wsgi.multithread`` has been changed such that it will now correctly report ``False`` if using embedded mode, a multithread capable MPM is used, but the number of configured threads is set to 1. + +* The ``graceful-timeout`` option for ``WSGIDaemonProcess`` now defaults to + 15 seconds. This was always the case when ``mod_wsgi-express`` was used + but the default was never applied back to the case where mod_wsgi was + being configured manually. + + A default of 15 seconds for ``graceful-timeout`` is being added to avoid + the problem where sending a SIGUSR1 to a daemon mode process would never + see the process shutdown due to there never being a time when there were + no active requests. This might occur when there were a stuck request that + never completed, or numerous long running requests which always overlapped + in time meaning the process was never idle. + + You can still force ``graceful-timeout`` to be 0 to restore the original + behaviour, but that is probably not recommended. |