From: Oliver Schad <oliver.schad@automatic-server.com>
To: supervision@list.skarnet.org
Subject: External health Check Process
Date: Thu, 22 Oct 2020 14:28:29 +0200 [thread overview]
Message-ID: <20201022142829.788f4da5@flunder> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Hi everybody,
we have cases, where processes are still there, but doesn't work
anymore. This is a common problem with runtime environments like java
or golang, where the memory management might have problems and internal
routines doesn't work anymore. That is really a common problem in that
area (heap too small, too frequently garbage collection, ...)
I know you can model a service in s6, which watches another service and
kills it, so in fact the problem is solved outside of s6. But I wanted
to ask to develop a feature to get a simple way to model that within s6.
Usually it's good enough to call a external command with a timeout and
watches exit code.
Yes, that means polling but in a datacenter is a polling health check
not a big energy problem.
Is that something, you can imagine in the future, supporting an
external health check?
Best Regards
Oli
--
Automatic-Server AG •••••
Oliver Schad
Geschäftsführer
Turnerstrasse 2
9000 St. Gallen | Schweiz
www.automatic-server.com | oliver.schad@automatic-server.com
Tel: +41 71 511 31 11 | Mobile: +41 76 330 03 47
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2020-10-22 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 12:28 Oliver Schad [this message]
2020-10-22 15:34 ` Laurent Bercot
2020-10-22 15:46 ` Casper Ti. Vector
2020-10-23 0:03 ` Steve Litt
2020-10-23 7:27 ` Oliver Schad
2020-10-23 9:15 ` Steve Litt
2020-10-23 13:44 ` Laurent Bercot
2020-10-23 17:03 ` Steve Litt
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=20201022142829.788f4da5@flunder \
--to=oliver.schad@automatic-server.com \
--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).