Gluster users - May 2011 - Increase cache lifetime on client

How can I prevent client to querying all glusterfs servers for updated
version of file and use version in a cache instead? I am using
glusterfs for webserving and even with opcode caching there are lots
of stat calls (it is nature of webapp I am running). I now myself when
I am updating code files and can invalidate cache with remounting or
by other way if it exist.

I am looking for client side option, not a volume/brick option as I
plan to mount some dirs in default mode and dont want to add more
complexity by adding another glusterfs volume.

In other words I want to prevent glusterfs of querying brick on every
request and use cached version instead. It is ok if such checks will
be once a min, but not on every request,please. Is it possible?

>
>
> In other words I want to prevent glusterfs of querying brick on every
> request and use cached version instead. It is ok if such checks will
> be once a min, but not on every request,please. Is it possible?
>
Yes, fuse provides such options. But sadly, mount.glusterfs doesn't handle
these options as of now. But you can start glusterfs process with all
options mount -t glusterfs will use, added with  "--entry-timeout 60"
and
"--attribute-timeout 60" (values are in seconds). As a warning note,
if you
are having lot of rename calls, (or many clients trying to create files with
same name (ie, path is same)), you may get some 'stale file handle' type
of
errors.

Regards,
Amar
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110523/2d6f5bfb/attachment.html>