[Lustre-devel] Flush on file close

Oleg Drokin oleg.drokin at oracle.com
Mon Apr 19 15:31:49 PDT 2010


On Apr 19, 2010, at 2:30 PM, Andrew Perepechko wrote:
> Since syncing may degrade performance to a large extent, what do you think is 
> the best/most convenient/least intrusive way to switch to that behaviour? 
> Should it be a mount option for the client or anything else?

Personally I think this is a non-issue for us.
There is no mad dash in other filesystems to implement this, aside from NFS where this
is what is guaranteed.
As long as we don't lose data after close (which we usually don't anyway) we are in the clear.
If we do (eviction, double failure) then there was some system exception that is kind of
similar to disk failure for regular fs.
Apps doing this "close after each write" should be fixed anyway because now they incur
additional overhead of two extra unneeded sync RPCs (open + close) and adding more overhead
to this is not going to help even if made optional.


More information about the lustre-devel mailing list