[Lustre-discuss] Newbie question: File locking, synchronicity, order, and ownership
Nochum Klein
nochum at gmail.com
Thu Jan 7 21:12:35 PST 2010
Hi Everyone,
Apologies for what is likely a simple question for anyone who has been
working with Lustre for a while. I am evaluating Lustre as part of a
fault-tolerant failover solution for an application component. Based on our
design using heartbeats between the hot primary and warm secondary
components, we have four basic requirements of the clustered file system:
1. *Write Order *- The storage solution must write data blocks to shared
storage in the same order as they occur in the data buffer. Solutions that
write data blocks in any other order (for example, to enhance disk
efficiency) do not satisfy this requirement.
2. *Synchronous Write Persistence* - Upon return from a synchronous
write call, the storage solution guarantees that all the data have been
written to durable, persistent storage.
3. *Distributed File Locking* - Application components must be able to
request and obtain an exclusive lock on the shared storage. The storage
solution must not assign the locks to two servers simultaneously.
4. *Unique Write Ownership* - The application component that has the
file lock must be the only server process that can write to the file. Once
the system transfers the lock to another server, pending writes queued by
the previous owner must fail.
Can anyone confirm that these requirements would be met by Lustre 1.8?
Thanks a lot!
Nochum
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20100108/deac861b/attachment.htm>
More information about the lustre-discuss
mailing list