From: Nicolas Williams <Nicolas.Williams@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] SOM safety
Date: Wed, 6 Jan 2010 11:28:13 -0600 [thread overview]
Message-ID: <20100106172812.GO1516@Sun.COM> (raw)
In-Reply-To: <4B44C3D5.8060701@sun.com>
On Wed, Jan 06, 2010 at 12:09:41PM -0500, Aleksandr Guzovskiy wrote:
> Eric Barton wrote:
> > 2. OST eviction
> >
> > An alternative to timeouts is to evict clients from the OSTs when
> > they are evicted from the MDS.
>
> This would be a step towards adding a notion of cluster membership to
> Lustre. Wouldn't there be other benefits from that in solving other
> races when client is evicted from one of the servers but is not evicted
> from others?
The health network will allow for eviction notices to be spread around
the cluster quickly.
I think we'll need a separate cluster membership capability for reasons
having to do with optimizing the health network: if you see a peer C
that's got a membership capability issued at time T_a and you're a
server S_n that's been in the cluster since before T_a and you've not
heard any eviction notices for C, then C is still a member of the
cluster. Without a cluster membership capability we'd need to ask the
health network if C is a member, and while that can happen quickly, in a
mostly-stateless health network (the current design) having every server
ask about the membership/liveness status of every peer client could
result in a load spike.
Nico
--
next prev parent reply other threads:[~2010-01-06 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 18:39 [Lustre-devel] SOM safety Eric Barton
2010-01-05 21:50 ` Andreas Dilger
2010-01-05 21:55 ` Nicolas Williams
2010-01-05 22:25 ` Oleg Drokin
2010-01-11 17:05 ` Vitaly Fertman
2010-01-06 17:09 ` Aleksandr Guzovskiy
2010-01-06 17:28 ` Nicolas Williams [this message]
2010-01-06 18:10 ` dzogin
2010-01-11 21:41 ` Vitaly Fertman
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=20100106172812.GO1516@Sun.COM \
--to=nicolas.williams@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.