Re: [Gluster-users] A Problem of readdir-optimize

>From Karan: > We had a similar issue when we were certifying gluster + milestone. But the issue got resolved when we disabled readdir-ahead. Looks like the >issue is in readdir code path. Paul, can you try turning off performance.readdir-ahead and see if the issue persists? On 29 December

Re: [Gluster-users] A Problem of readdir-optimize

Hi Nithya, GlusterFS version is 3.11.0, and we use the native client of GlusterFS. Please see the below information. $gluster v info vol Volume Name: vol Type: Distributed-Replicate Volume ID: d59bd014-3b8b-411a-8587-ee36d254f755 Status: Started Snapshot Count: 0 Number of Bricks: 90 x 2 = 180

Re: [Gluster-users] A Problem of readdir-optimize

Hi Paul, A few questions: What type of volume is this and what client protocol are you using? What version of Gluster are you using? Regards, Nithya On 28 December 2017 at 20:09, Paul wrote: > Hi, All, > > If I set cluster.readdir-optimize to on, the performance of "ls" is >

[Gluster-users] A Problem of readdir-optimize

Hi, All, If I set cluster.readdir-optimize to on, the performance of "ls" is better, but I find one problem. # ls # ls files.1 files.2 file.3 I run ls twice. At the first time, ls returns nothing. At the second time, ls returns all file names. If turn off cluster.readdir-optimize, I don't see