public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Alan Coopersmith <alan.coopersmith@oracle.com>
To: developer@lists.illumos.org
Subject: Re: [developer] Review - 15665 svc:/network/loopback exits successfully even if it fails
Date: Fri, 26 Jul 2024 11:08:39 -0700	[thread overview]
Message-ID: <b946fb9c-bb9f-41d1-8220-112c5977b906@oracle.com> (raw)
In-Reply-To: <CAEgYsbFG=qUJVjUeSLg76syCxmTAqum-NipGgtcMBoK1HVaO-g@mail.gmail.com>

On 7/26/24 08:14, 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.
> 
> So the equivalent of SMF_EXIT_DEGRADED might be what we're looking for?

SMF_EXIT_DEGRADED was added in Solaris 11.4, but the degraded mode existed long
before that - see for instance smf_degrade_instance() on
https://illumos.org/man/3SCF/smf_degrade_instance and the states section of
https://illumos.org/man/7/smf .

The addition of SMF_EXIT_DEGRADED allows start, stop, and refresh methods to
put the service into degraded mode, since otherwise they'd have to return an
exit code that put the service into one of the other modes (online, offline,
maintenance), and then have something else wait for the method to finish and
then call smf_degrade_instance(), which could lead to race conditions or
incorrect actions being taken during the brief moment the service is in the
wrong state before going to degraded mode.

	-alan-

  parent reply	other threads:[~2024-07-26 18:08 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 [this message]
2024-08-07 20:04       ` Andy Fiddaman
2024-09-09 17:36         ` Andy Fiddaman

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=b946fb9c-bb9f-41d1-8220-112c5977b906@oracle.com \
    --to=alan.coopersmith@oracle.com \
    --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).