Re: Read from fastest node only

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

 



Hi David,

md-cache will just save some lookup actions across the bricks, but it won't save you from all cases.

Using gNFS + cluster.choose-local is worth exploring, but as gNFS is deprecated I never checked if it will be affected by the lattency of the last brick.

What Ravi proposed looks promising, but it has some drawbacks - for example a brick dies and FUSE clienta have to be adjusted to read from another brick.

Ravi, I think that this topic was already discussed once.

Best Regards,
Strahil Nikolov

On Fri, Jul 30, 2021 at 8:49, Ravishankar N
<ranaraya@xxxxxxxxxx> wrote:
________



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

________



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