All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel Rutman <Nathan.Rutman@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [Lustre-discuss] Start the MGS first?
Date: Wed, 01 Apr 2009 08:16:40 -0700	[thread overview]
Message-ID: <49D38558.2040709@sun.com> (raw)
In-Reply-To: <1238103314.4115.11.camel@sledge.emsl.pnl.gov>

Kevin Fox wrote:
> On Wed, 2009-03-25 at 12:48 -0700, Nathaniel Rutman wrote:
>   
>> As of Lustre 1.6, servers can be started in any order (after the
>> initial registration at first startup).  Internally, this required
>> significant bending of our connection rules, and with a move toward
>> ZFS becomes even more burdensome. 
>> So my question to the Lustre community is this: would anyone
>> strenuously object to a startup ordering requirement that the MGS must
>> be started before any other servers? 
>> This would probably be in the Lustre 3.0 timeframe.  It is also likely
>> that we will have to divorce the MGS and MDT onto separate devices --
>> no more "combo" MDT/MGSes.
>>
>>     
>
> "server startup" being, things wont start working until the MGS is up,
> or, server startup commands will fail if the MGS is not up?
>
> The former, is much better then the latter. It allows the system to
> potentially bring itself back up automatically if things get rebooted
> (power bump, spike, etc).
>
>   
The former.  Server mount commands would just block until the MGS was 
available (probably with an optional timeout).  So the only thing that 
would fail is serialized startup of OST before MGS -- independent, 
unordered startup would sort itself out.
> Kevin
>
>   
>>>>  NR> I think the only reason to have a local config file is to be
>>>>         
>> able to
>>     
>>>>  NR> start a server in the absence of the MGS.  How much effort do
>>>>         
>> we want
>>     
>>>>  NR> to expend to be able to keep that ability?  I don't think
>>>>         
>> it's a huge
>>     
>>>>  NR> burden to say "MGS must be started first".
>>>>         
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>
>>
>>     
>
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>   

      reply	other threads:[~2009-04-01 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 19:48 [Lustre-devel] Start the MGS first? Nathaniel Rutman
2009-03-25 20:00 ` Brian J. Murrell
2009-04-01 15:13   ` Nathaniel Rutman
2009-03-25 20:15 ` Nicholas Henke
2009-03-26 21:35 ` [Lustre-devel] [Lustre-discuss] " Kevin Fox
2009-04-01 15:16   ` Nathaniel Rutman [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=49D38558.2040709@sun.com \
    --to=nathan.rutman@sun.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.