Bug #78742 [Fbk->Opn]: each php sleep() creates new fpm-child-process
| From: | michael_bliem at gmx dot at | Date: | Thu, 07 Nov 2019 07:29:42 +0000 |
| Subject: | Bug #78742 [Fbk->Opn]: each php sleep() creates new fpm-child-process | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-223616@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=78742&edit=1
ID: 78742
User updated by: michael_bliem at gmx dot at
Reported by: michael_bliem at gmx dot at
Summary: each php sleep() creates new fpm-child-process
-Status: Feedback
+Status: Open
Type: Bug
Package: FPM related
Operating System: debian buster VM
PHP Version: 7.3.10
Block user comment: N
Private report: N
New Comment:
it does not scale!
e.g.: if there is a sleep(1h) in a php-file and pm.max_children+1 clients call this php-file, the
last one receives a 503-response! additionally for 1h the page will be offline (503) as all
child-processes are idle for one hour...
Previous Comments:
------------------------------------------------------------------------
[2019-11-06 16:07:02] sjon@php.net
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php
If you can provide more information, feel free to add it
to this bug and change the status back to "Open".
Thank you for your interest in PHP.
this is expected - a sleeping child cannot handle other requests so php-fpm will create a new child
to handle new requests. Why did you think this is a bug?
------------------------------------------------------------------------
[2019-10-23 15:10:39] michael_bliem at gmx dot at
Description:
------------
standard installation of:
-debian buster
-php7.3-fpm
-apache2
each php-sleep seems to trigger creation of a new fpm-child-process.
this results in 503 errors when there are many requests if no more child-processes can be created
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=78742&edit=1