ab50b54169
We've noticed that our static sites will semi-regularly have problems due to stale SSL certs served by Apache workers which predate the latest certificate replacement and haven't terminated (graceful restart only ends the running workers once they have no remaining connections). Limit the impact of this by recycling workers automatically after a reasonable (large) number of connections. This implementation is shamelessly stolen from that used in Ic377f48d1a5a3eecbcb183327c9255134c4364ab for our mirror sites. Change-Id: I2e5c0bdf012184ebbfccb086b967008bf12582ab Co-Authored-By: Clark Boylan <clark.boylan@gmail.com>
15 lines
607 B
Plaintext
15 lines
607 B
Plaintext
# worker MPM
|
|
# MaxConnectionsPerChild: maximum number of requests a server process serves
|
|
#
|
|
# We've noticed that our mirrors occasionally have stale workers. This leads
|
|
# to ssl certs not being refreshed properly after reload and we've also seen
|
|
# ssl connections to round robin backend services have trouble. Restarting
|
|
# the workers so that they load up new info seems to fix this. Try and force
|
|
# that to happen regularly with a connections limit per worker.
|
|
<IfModule mpm_worker_module>
|
|
MaxConnectionsPerChild 8192
|
|
</IfModule>
|
|
<IfModule mpm_event_module>
|
|
MaxConnectionsPerChild 8192
|
|
</IfModule>
|