Re: [PATCH] Prevent OOM from killing init

Stephen Clouse
2001-03-25T07:00:53Z

[-- Attachment #1: msg.pgp --]
[-- Type: text/plain, Size: 1869 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Mar 24, 2001 at 09:45:01PM -0800, Stephen Satchell wrote:
> If you have a mission-critical application running on your box, add it to
> the inittab file with the RESPAWN attribute. That way, OOM killer kills
> it, init notices it, and init restarts your server.

Ah, that's great for simple daemons. Now tell me how to help an app like this
(Oracle exampled here):

oracle 89 0.0 0.4 41076 1776 ? S Mar22 0:00 ora_pmon_slash
oracle 91 0.0 0.6 40676 2620 ? S Mar22 0:00 ora_dbw0_slash
oracle 93 0.0 0.4 40544 1788 ? S Mar22 0:00 ora_lgwr_slash
oracle 95 0.0 0.4 40544 1744 ? S Mar22 0:00 ora_ckpt_slash
oracle 97 0.0 1.1 40556 4404 ? S Mar22 0:00 ora_smon_slash
oracle 99 0.0 0.5 40536 2188 ? S Mar22 0:00 ora_reco_slash
oracle 101 0.0 0.4 40656 1756 ? S Mar22 0:00 ora_arc0_slash

In this example, when oom_kill reaps one of these autonomous threads, Oracle
opts to crash and burn. Database corruption is almost guaranteed.

In all reality, I'm sure any daemon (threads or no) that works heavily with disk
files is likely to screw itself and its data if it gets sigkilled for no
reason. And in our environment, there is no reason for it to get sigkilled.

I'm going to severely hurt the first person that says such a program should be
*expecting* random untrappable annihilation of its threads. (And what happens
when the master process *is* the target?)

- --
Stephen Clouse <stephenc@theiqgroup.com>
Senior Programmer, IQ Coordinator Project Lead
The IQ Group, Inc. <http://www.theiqgroup.com/>

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBOr2XDgOGqGs0PadnEQK0rACfQELDid11+m90bS/DrGyrsHW45ZEAn19G
mL3fSCdi2TeHDxGLA8uXT8l5
=oQPV
-----END PGP SIGNATURE-----