On 24/04/20 11:42 am, David Cunningham
wrote:
I assume you are talking about replica volumes, in which case the read does happen from only one of the replica bricks. The client only sends lookups to all the bricks to figure out which are the good copies. Post that, the reads themselves are served from only one of the good copies.Hello,
My understanding is that GlusterFS checks with all nodes when performing a read. Is it possible to just get the data from the node directly being accessed (in our case using the GlusterFS client), without consulting with the other nodes?
Our application requires the GFS file to be available, but it's actually not critical if we end up with an old version of the file in the case of a server down or net-split etc. Significantly improved read performance would be desirable instead.
-Ravi
Thanks in advance for any help.
--
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 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://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
