From: dzogin <Dmitri.Zoguine@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] SOM safety
Date: Wed, 06 Jan 2010 13:10:40 -0500 [thread overview]
Message-ID: <4B44D220.7070906@sun.com> (raw)
In-Reply-To: <20100106172812.GO1516@Sun.COM>
Nicolas Williams wrote:
> 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.
>
I think this can be easily implemented as a bitmap on every server (both
OSS and MDS) that keeps track of the alive and evicted clients. Once you
have processed all the amount of work that needs to be done for the
client that has been evicted, that bit in the evicted clients map is
cleared. Instead of sending the information about every client, servers
can exchange the bitmaps, and doing XOR on bitmaps would allow you to
easily see the discrepancies in client evictions.
I think the same idea of bitmaps can be implemented for objects, if we
want to track which client is updating the object/stripe.
Dmitry
next prev parent reply other threads:[~2010-01-06 18:10 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
2010-01-06 18:10 ` dzogin [this message]
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=4B44D220.7070906@sun.com \
--to=dmitri.zoguine@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.