[Gluster-devel] xlator.mount.fuse.itable.lru_limit=0 at client fuse process

Dear, Developers, Many tuning and benchmark on different gluster release, 3.12.15, 4.1, 3.11, the client fuse process will eat hundreds of GB RAM memory with 256G memory system, then OOM and was killed at some time. To consult many google search, fuse related paper, benchmark, testing, We can n

Re: [Gluster-devel] Any mature(better) solution(way) to handle slow performance on 'ls -l, '.

known > issues. > > Regards, > Poornima > > [1] > https://github.com/gluster/glusterdocs/pull/342/files#diff-62f536ad33b2c2210d023b0cffec2c64 > > On Wed, May 30, 2018, 8:29 PM Yanfei Wang wrote: >> >> Hi experts on glusterFS, >> >> In our testbed, we f

[Gluster-devel] Any mature(better) solution(way) to handle slow performance on 'ls -l, '.

Hi experts on glusterFS, In our testbed, we found that the ' ls -l' performance is pretty slow. Indeed from the prospect of glusterFS design space, we need to avoid 'ls ' directory which will traverse all bricks sequentially in our current knowledge. We use generic setting for our testbed: ``` V

[Gluster-devel] How gluster handle split-brain in the corner case from non-overlapping range lock in same file?

Hi, https://docs.gluster.org/en/v3/Administrator%20Guide/arbiter-volumes-and-quorum/, said, ``` There is a corner case even with replica 3 volumes where the file can end up in a split-brain. AFR usually takes range locks for the {offset, length} of the write. If 3 writes happen on the same file a