All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian J. Murrell <Brian.Murrell@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Start the MGS first?
Date: Wed, 25 Mar 2009 16:00:40 -0400	[thread overview]
Message-ID: <1238011240.6090.16.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <49CA8A73.9080103@sun.com>

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. 

I'll ask before anyone else does... would this require the MGS be
available at any time a server (or client?) needs to start rather than
the optional behaviour (for anything but first time server starts) that
we currently enjoy?  IOW, does this make the MGS a much more critical
component of the filesystem than it is currently?

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20090325/67ee0ef3/attachment.pgp>

  reply	other threads:[~2009-03-25 20:00 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 [this message]
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

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=1238011240.6090.16.camel@pc.interlinx.bc.ca \
    --to=brian.murrell@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.