view mod_graceful_shutdown/README.markdown @ 4877:adc6241e5d16

mod_measure_process: Report the enforced limit The soft limit is what the kernel actually enforces, while the hard limit is is how far you can change the soft limit without privileges. Unless the process dynamically adjusts the soft limit, knowing the hard limit is not as useful as knowing the soft limit. Reporting the soft limit and the number of in-use FDs allows placing alerts on expressions like 'process_open_fds / process_max_fds >= 0.95'
author Kim Alvefur <zash@zash.se>
date Tue, 18 Jan 2022 18:55:20 +0100
parents 88474dd1af48
children 999e7cb7f6d9
line wrap: on
line source

This module is an experiment about a more graceful shutdown process.

Why
===

When shutting down, a number of sessions, connections and other things
are teared down. Due to all these things happening very quickly,
sometimes e.g. client unavailable notifications don't make it to all
remote contacts because the server-to-server connections are teared down
just after.

How
===

This module works by breaking the shutdown process into separate steps
with a brief pause between them.

It goes something like this

1.  Stop accepting new client connections.
2.  Close all client connections.
3.  Fire event for everything else.
4.  Tell `net.server` to quit the main loop.
5.  ???
6.  Still here? Kill itself.