[Gluster-users] Increased brick 'activity' when moving 3.2.5->3.3.0

David Coulson david at davidcoulson.net
Fri Jun 1 16:28:11 UTC 2012

I upgraded my 3.2.5 environment to 3.3.0 this morning. I'm seeing an approx 4x increase in network activity since the upgrade. tcpdump indicates a volume which is pretty much 100% reads has a lot of tcp activity between the nodes. Since it is mounted NFS, I was expecting that for a 'nearly all read' workload it would utilize the OS cache (this is what I experienced when we moved from Fuse to NFS under 3.2.5).

Is there a volume tweak or a change to NFS I need to make to utilize OS caching? We're running on RHEL6. Here is my mount output for this volume.

localhost:/ldirectord on /etc/ldirectord type nfs (rw,noatime,nodiratime,tcp,vers=3,nolock,addr=


More information about the Gluster-users mailing list