From: Peter J Braam <Peter.Braam@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Global generic database
Date: Thu, 14 Feb 2008 07:57:16 -0700 [thread overview]
Message-ID: <47B456CC.6090400@sun.com> (raw)
In-Reply-To: <47B335B6.5010703@sun.com>
Hmm ... here are my thoughts.
1. The word scalable is missing below.
2. Any database that relates to file system policies and file system
objects (HSM?) should be a separate mechanism coupled to the file
system, so that you can pick up the server disks and the policies.
3. I think all updates to the database should be made on the server, and
the use cases should be restricted (e.g. this is for relatively small
databases).
4. Imho pools belong in the configuration log.
5. Fileset attributes belong with the file system (see 2) - either these
are implemented as special directory files and/or EA's (does the design
specify the purpose and items that need to be stored in databases?).
Hmm, so can we revisit why we need a new database mechanism?
- Peter -
Nathaniel Rutman wrote:
> The design of various new features in Lustre call for global (filesystem
> wide) databases, accessible from
> clients or other servers:
> A. pools - pool descriptions (pool #1 = OSTs 1-10,30-60), pool policies
> (all .jpg files to pool #1)
> B. filesets - fileset policies (log creates on fileset #1 to feed "foo")
> C. HSM - (aureleien - what was the use case here?)
>
> We've already implemented at least 2 of these:
> D. Fid Location Database - (is this done?)
> E. configuration parameters - stored in MGS llogs
>
> Rather than continue 1-off implementations, I think it's time we came up
> with a consistent,
> global, generic database mechanism for A-C as well as other future uses.
> Needs to be:
> 1. Fast. We need to cache database entries locally, which also means
> having them under locks.
> a. local caching
> b. locks
> 2. Generic. Store any kind of data, not limited to 8k page boundaries, etc.
> 3. Transactional. Power loss doesn't lead to inconsistent state.
> 4. Recoverable. Client changes are replayed if need be.
> 5. Remotely accessible, from a client or other servers.
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>
next prev parent reply other threads:[~2008-02-14 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 18:23 [Lustre-devel] Global generic database Nathaniel Rutman
2008-02-13 20:35 ` Canon, Richard Shane
2008-02-14 12:58 ` Aurelien Degremont
2008-02-14 14:57 ` Peter J Braam [this message]
2008-02-14 19:56 ` Nathaniel Rutman
2008-02-15 3:32 ` Peter J Braam
2008-02-15 20:40 ` Nikita Danilov
2008-02-15 17:50 ` Alexander Zarochentsev
2008-02-16 7:40 ` Andreas Dilger
2008-02-17 11:27 ` Alex Lyashkov
2008-02-18 21:57 ` Yuriy Umanets
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=47B456CC.6090400@sun.com \
--to=peter.braam@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.