All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Horn <hornc@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Imperative Recovery - forcing failover server stop blocking
Date: Fri, 19 Jun 2009 17:10:58 -0500	[thread overview]
Message-ID: <4A3C0CF2.1080809@cray.com> (raw)
In-Reply-To: <447088AD-0C97-4314-A5AA-D7179C9C5C63@sun.com>

Oops, I forgot to cc lustre-devel.

Johann Lombardi wrote:

> > On Jun 19, 2009, at 1:10 AM, Chris Horn wrote:
>   
>> >> It seems as though an ability to short circuit is only going to be
>> >> useful if we can distinguish between the case where we only need a short
>> >> recovery window vs. the case where we need that extra time.  My question
>> >> is, what are the use cases where this applies?
>> >>
>> >> My intuition is the following:
>> >> Case 1:  x/y clients which are dead, (y-x)/y clients connected to the
>> >> backup server (all clients that can connect have done so).  We want to
>> >> go ahead and short circuit.
>>     
> >
> > That's the 2nd aspect of imperative recovery. We want to notify the
> > server when all clients that were supposed to reconnect should
> > have done so already. Basically, the idea is to tell the server that
> > no new clients will reconnect now and that it is not needed to wait
> > any longer for new clients to join (the x clients).
>   
I just want to verify that in order to use this 2nd aspect of imperative
recovery we need some method of determining client health, yes?


Chris Horn

  reply	other threads:[~2009-06-19 22:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 23:10 [Lustre-devel] Imperative Recovery - forcing failover server stop blocking Chris Horn
2009-06-19 21:18 ` Johann Lombardi
2009-06-19 22:10   ` Chris Horn [this message]
2009-06-22 17:53     ` Eric Barton
2009-06-22 18:21       ` Chris Horn
2009-06-22 19:27         ` Brian Behlendorf
2009-06-23 12:49         ` Eric Barton
2009-06-23 14:53           ` Andreas Dilger
2009-06-23 14:59             ` Chris Horn
2009-06-23 17:20             ` Robert Read

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=4A3C0CF2.1080809@cray.com \
    --to=hornc@cray.com \
    --cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.