Thanks, Krutika!
So, if I understand you correctly...if both Brick 1 and Brick 2 have a good copy of the file, then we can't tell for sure if the file will be read only from Brick 1 all the time and not Brick 2? in other words, for read#1, the file could be read from brick
2 and for another read which could happen a few minutes later, the file could be read from brick 1? From: Krutika Dhananjay <kdhananj@xxxxxxxxxx>
Sent: Friday, April 10, 2015 9:30 PM To: Bharathram Sivasubramanian Cc: Gluster-users@xxxxxxxxxxx Subject: Re: Question on file reads from a distributed replicated volume From: "Bharathram Sivasubramanian" <Bharathram.Sivasubramanian@xxxxxxxxxxx> A given file will consistently be "read" from one of the N (in this case 2) replicas, as long as it holds a good copy of the file (that which does not need heal), even with client restart. We call it the "read child" of the file. Load
balancing within a volume is done across different files wherein different files would have different but constant read children.
-Krutika
_______________________________________________ |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users