From: Andy Fiddaman <illumos@fiddaman.net>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] Review - 15665 svc:/network/loopback exits successfully even if it fails
Date: Mon, 9 Sep 2024 17:36:02 +0000 (UTC) [thread overview]
Message-ID: <9c0ae5cf-6187-4904-b662-1d81c48a71e1@fiddaman.net> (raw)
In-Reply-To: <af65ca14-de89-41a0-b26a-13f7e0cd44d8@fiddaman.net>
On Wed, 7 Aug 2024, Andy Fiddaman wrote:
>
> On Fri, 26 Jul 2024, Peter Tribble wrote:
>
> > As I mentioned in my other reply, it seems that what we're after is some
> > way to mark
> > a service as having generated an error without bringing the system down by
> > going
> > into maintenance. Some sort of degraded mode.
> >
> > We have a couple of SMF exit codes that look interesting -
> > SMF_EXIT_MON_DEGRADE
> > and SMF_EXIT_MON_OFFLINE, but I'm sure they were never implemented. There's
> > even an issue in this area - https://www.illumos.org/issues/7711 (which
> > refers back to 8891
> > which is another case of something dropping into maintenance breaking the
> > entire system).
>
> I have put up https://code.illumos.org/c/illumos-gate/+/3621 which is
> resurrecting work by Andy Stormont to add the missing pieces to support
> degraded services, and then re-worked
> https://code.illumos.org/c/illumos-gate/+/3610/
> on top of that.
>
> This does seem like the best solution - the service does what it can and
> doesn't block others from coming up, yet it shows up as degraded in
> `svcs -x` and co.
>
> My testing's going well so I'll get that sent out for review in the next
> couple of days.
>
> Thanks for all the discussion and feedback on this change!
Now that https://www.illumos.org/issues/7711 has integrated, I am planning
to send the latest version of this for RTI:
15665 svc:/network/loopback exits successfully even if it fails
https://www.illumos.org/issues/15665
https://code.illumos.org/c/illumos-gate/+/3610
This now uses the SMF degraded state rather than maintenance as the original
change did. I think this should address the concerns that were raised and,
again, thanks for the discussions around this.
Andy
prev parent reply other threads:[~2024-09-09 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 8:20 Andy Fiddaman
2024-07-26 12:44 ` [developer] " Peter Tribble
2024-07-26 13:41 ` Toomas Soome
2024-07-26 14:05 ` Peter Tribble
2024-07-26 13:50 ` Andy Fiddaman
2024-07-26 15:14 ` Peter Tribble
2024-07-26 15:55 ` Jorge Schrauwen
2024-07-30 22:46 ` Gordon Ross
2024-07-31 9:44 ` Peter Tribble
2024-08-01 8:48 ` Joshua M. Clulow
2024-07-26 18:08 ` Alan Coopersmith
2024-08-07 20:04 ` Andy Fiddaman
2024-09-09 17:36 ` Andy Fiddaman [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=9c0ae5cf-6187-4904-b662-1d81c48a71e1@fiddaman.net \
--to=illumos@fiddaman.net \
--cc=developer@lists.illumos.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).