On 08/10/2016 05:12 PM, Deepak Naidu wrote:
Before we can try physical we wanted POC on VM.
Just a note the VMs are decently powerful 18cpus, 10gig NIC, 45GB Ram 1TB SSD drives. This is per node spec.
I don't see the ls -l command hanging when I try to list the files from the gluster-node VMs itself So the question.
The reason I alluded to a physical setup was to remove the variables
that can affect performance in a virtual setup. The behavior is not
usual for the scale of deployment that you mention. You could use strace
in conjunction with gluster volume profile to determine where the
latency is stemming from.
Regards,
Vijay
--
Deepak
On Aug 10, 2016, at 2:01 PM, Vijay Bellur <vbellur@xxxxxxxxxx> wrote:
On 08/10/2016 04:54 PM, Deepak Naidu wrote:
Anyone who has seen the issue in their env ?
--
Deepak
-----Original Message-----
From: gluster-users-bounces@xxxxxxxxxxx [mailto:gluster-users-bounces@xxxxxxxxxxx] On Behalf Of Deepak Naidu
Sent: Tuesday, August 09, 2016 9:14 PM
To: gluster-users@xxxxxxxxxxx
Subject: Linux (ls -l) command pauses/slow on GlusterFS mounts
Greetings,
I have 3node GlusterFS on VM for POC each node has 2x bricks of 200GB. Regardless of what type of volume I create when listing files under directory using ls command the GlusterFS mount hangs pauses for few seconds. This is same if there're 2-5 19gb file each or 2gb file each. There are less than 10 files under the GlusterFS mount.
I am using NFS-Ganesha for NFS server with GlusterFS and the Linux client is mounted using GlusterFS fuse mount with direct-io enabled.
GlusterFS version 3.8(latest)
Any insight is appreciated.
This does not seem usual for the deployment that you describe. Can you try on a physical setup to see if the same behavior is observed?
-Vijay
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
