On 17-05-15 13:40, John Spray wrote:
On Mon, May 15, 2017 at 10:40 AM, Ranjan Ghosh <ghosh@xxxxxx> wrote:
Hi all,
When I run "ceph daemon mds.<name> session ls" I always get a fairly large
number for num_caps (200.000). Is this normal? I thought caps are sth. like
open/locked files meaning a client is holding a cap on a file and no other
client can access it during this time.
Capabilities are much broader than that, they cover clients keeping
some fresh metadata in their cache, even if the client isn't doing
anything with the file at that moment. It's common for a client to
accumulate a large number of capabilities in normal operation, as it
keeps the metadata for many files in cache.
You can adjust the "client cache size" setting on the fuse client to
encourage it to cache metadata on fewer files and thereby hold onto
fewer capabilities if you want.
John
Is there an option (or planned option) for clients to release caps after
some time of inuse?
In my testing I saw that clients tend to hold on caps for indefinite time.
Currently in prod I have use case where are over 8mil caps and little
over 800k inodes_with_caps.
How can I debug this if it is a cause
of concern? Is there any way to debug on which files the caps are held
excatly?
Thank you,
Ranjan
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
