Summary: | httpd kills keepalive connections when idle workers available | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | mkempski |
Component: | mpm_event | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | NEW --- | ||
Severity: | regression | ||
Priority: | P2 | ||
Version: | 2.4.37 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
mkempski
2023-05-26 10:47:18 UTC
Thread in the mailing list with additional information: https://lists.apache.org/thread/156tzy45crd0kqsr988rn4hvdcvm6skc > httpd seems to not register that it has free workers even when I set StartServers to 120
startservers only controls how many are created at startup. Every second, min/max spare threads will be checking how many processes need to be stopped or started.
The problem on your system seems to be that additional processes aren't being spun up.
Did you have a look at https://httpd.apache.org/docs/2.4/mod/event.html#asyncrequestworkerfactor ? (In reply to Eric Covener from comment #2) > > httpd seems to not register that it has free workers even when I set StartServers to 120 > > startservers only controls how many are created at startup. Every second, > min/max spare threads will be checking how many processes need to be stopped > or started. > > The problem on your system seems to be that additional processes aren't > being spun up. Yes it does not spawn enough. Even if I force it to start with maximum values the problem persists. Only changing ThreadsPerChild to much higher number and starting with enough servers to handle peak has an effect. What is the reason for this behavior? (In reply to Ruediger Pluem from comment #3) > Did you have a look at > https://httpd.apache.org/docs/2.4/mod/event.html#asyncrequestworkerfactor ? Yes, changing this setting to higher or lower values than default does not resolve this problem. |