Bug 66214 - Huge memory utilization after upgrade from 2.3.39 to 2.4.54
Summary: Huge memory utilization after upgrade from 2.3.39 to 2.4.54
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.4.53
Hardware: PC All
: P2 critical (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-13 16:51 UTC by inf
Modified: 2022-08-23 15:03 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description inf 2022-08-13 16:51:06 UTC 
Whereas 2.4.39 used ~250 MB 2.4.54 uses 5.7 GB and keeps growing.
Comment 1 inf 2022-08-14 23:20:18 UTC 
The instance is now at 9 GB and growing.
Comment 2 engrand 2022-08-23 15:03:00 UTC 
Did you find any solution ?

We have the same issue, our architecture is the following:

* apache run in foreground mode inside a docker container
* apache run behind haproxy with option forceclose
* Use of mpm_event with the following configuration:

  StartServers           3
  ServerLimit            16
  ThreadLimit            32
  MinSpareThreads        25
  MaxSpareThreads        32
  ThreadsPerChild        32
  MaxRequestWorkers      512
  MaxConnectionsPerChild 1024

  Keepalive On

The number of children grows up until the limit then the server cannot serves request anymore. With mpm_worker, the number of children grows up infinitely. As consequences, the memory usage also grows up.
It seems, it is not the gracefully stop problem, because apache status does not show a such situation.

As workaround, we just set MaxConnectionsPerChild to 0.

Thank you for your help.