[Lustre-devel] [RFC] two ideas for Meta Data Write Back Cache
Eric Barton
eeb at sun.com
Mon May 18 14:01:15 PDT 2009
Zam,
A couple of things to consider when splitting up operations
into updates....
1. Each update must contain some information about its peer
updates so that in the absence of the client (e.g. on
client eviction) we can check that all the operations's
updates have been applied and apply a correction if not.
I think there is an advantage if every update includes
sufficient information to reconstruct all its peer
updates.
2. The current security design grants capabilities to clients
to perform operations on Lustre objects. If you allow
remote "raw" OSD ops, you're effectively distributing the
Lustre clustered server further - i.e. nodes allowed to
do such operations are being trusted just as much as
servers to keep the filesystem consistent.
Cheers,
Eric
More information about the lustre-devel
mailing list