[Bugs] [Bug 1166862] New: rmtab file is a bottleneck when lot of clients are accessing a volume through NFS
bugzilla at redhat.com
bugzilla at redhat.com
Fri Nov 21 18:53:21 UTC 2014
https://bugzilla.redhat.com/show_bug.cgi?id=1166862
Bug ID: 1166862
Summary: rmtab file is a bottleneck when lot of clients are
accessing a volume through NFS
Product: GlusterFS
Version: 3.5.2
Component: nfs
Severity: urgent
Assignee: bugs at gluster.org
Reporter: cyril at peponnet.fr
CC: bugs at gluster.org, gluster-bugs at redhat.com
Created attachment 959917
--> https://bugzilla.redhat.com/attachment.cgi?id=959917&action=edit
Load average
Description of problem:
This feature: http://review.gluster.org/#/c/4430/
Create bottleneck when several clients are accessing a nfs volume.
On our setup:
Gluster 3.5.2 under centos7.
Hardware:
dual Xeon® CPU E5-2640
64GB RAM
SSD for rootfs
10Gb NIC
Context:
Around 700 nfs clients for small file or vm images.
Version-Release number of selected component (if applicable):
3.5.2
How reproducible:
Always as long as you have enough NFS clients
Steps to Reproduce:
1. Create a volume accessible through gluster nfs
2. Make it accessible for 700 clients
3. See how it hangs
Actual results:
NFS client got intermittent hang (every minutes / for 10s each time). Even an
“rpcinfo -t server nfs 3" will hang.
Gluster nfs process literally eat the CPU of the server
Expected results:
No hanging
Additional info:
The cause:
the rmtab file located in /var/lib/glusterd/nfs/ is flushed from memory to
/var/lib/glusterd/nfs/rmtab.tmp. During this time, NFS server hang literraly.
Workaroud:
Move the file to memory for faster I/O using this option:
set nfs.mount-rmtab: /dev/shm/glusterfs.rmtab
Result:
We still have some hang but for ~300ms now, the load average of the server is
WAY better.
Personal thought:
This feature is not usable and should be disabled by default.
You can find attached load average and Disk usage before and after using SHM
for rmtab.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list