cluster.readdir-optimize

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am trying to understand how cluster.readdir-optimize works
on a full replica N volume.

https://lists.gluster.org/pipermail/gluster-devel/2016-November/051417.html

suggests that this setting can be useful on distributed
volumes. On full replica volumes, every brick has 100% of
the information required by readdir, so logically every
request should be satisfied locally without any network
traffic between bricks even if cluster.readdir-optimize
is off. Is that not the case?

Z

________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux