From: Dewayne <dewayne.geraghty@heuristicsystems.com.au>
To: supervision@list.skarnet.org
Subject: Re: "Back off" setting for crashing services with s6+openrc?
Date: Tue, 11 Oct 2022 11:38:19 +1100 [thread overview]
Message-ID: <cd0dde66-4ca5-9100-0017-6efd848e7bc6@heuristicsystems.com.au> (raw)
In-Reply-To: <emb087a60d-4590-4260-bfba-cf19c1c83ee5@5e65708a.com>
On 30/09/2022 11:21 pm, Laurent Bercot wrote:
> A service that keeps crashing is an abnormal condition
Yes - sometimes that's what villains like to do :)
> Note that I don't think making the restart delay configurable is a good
> trade-off. It adds complexity, size and failure cases to the s6-supervise
> code, it adds another file to a service directory for users to remember,
> it adds another avenue for configuration mistakes causing downtime, all
> that to save resources for a pathological case. The difference between
> 0 second and 1 second of free CPU is significant; longer delays have
> diminishing returns.
I'm not sure that its entirely pathological, as I also use 'finish' with
a 'sleep' and timeout-finish in an effort to reduce SROP issues. Its
also fairly common for us to have a loadavg of 4x ncores.
In the general case, yes if you want a process running then it should be
up asap, and for that I'm very appreciative. :)
Ref:
For ROP https://en.wikipedia.org/wiki/Return-oriented_programming
SROP https://www.cs.vu.nl/~herbertb/papers/srop_sp14.pdf
prev parent reply other threads:[~2022-10-11 0:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 19:45 Tor Rune Skoglund
2022-09-22 20:21 ` John W Higgins
2022-09-23 7:29 ` Tor Rune Skoglund
2022-09-23 16:44 ` Alyssa Ross
2022-09-24 12:33 ` Oliver Schad
2022-09-26 23:00 ` Colin Booth
2022-09-30 9:34 ` Oliver Schad
2022-09-30 13:21 ` Laurent Bercot
2022-10-04 14:16 ` Tor Rune Skoglund
2022-10-10 16:20 ` Laurent Bercot
2022-10-11 0:38 ` Dewayne [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd0dde66-4ca5-9100-0017-6efd848e7bc6@heuristicsystems.com.au \
--to=dewayne.geraghty@heuristicsystems.com.au \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).