Le 04/03/2016 13:12, Krutika Dhananjay a écrit :
You could configure read-subvolume for individual clients using the following mount option:mount -t glusterfs -o "xlator-option=*replicate*.read-subvolume-index=0" <hostname>:/<volname> <mountpoint>In the example above, 0 represents the zeroth child. If a particular client wants to use the second brick as the read child, use the following:mount -t glusterfs -o "xlator-option=*replicate*.read-subvolume-index=1" <hostname>:/<volname> <mountpoint>
Thanks for that tip!Just a question: as our clients can migrate beetween buildings (not often, but it happens), does using something like 'mount -o "remount,xlator-option=*replicate*.read-subvolume-index=X" …' will allow the client to point to the new target without stopping volume availability for clients?
-- Y.
-Krutika
------------------------------------------------------------------------
*From: *"Yannick Perret" <yannick.per...@liris.cnrs.fr>
*To: *"Krutika Dhananjay" <kdhan...@redhat.com>
*Cc: *gluster-users@gluster.org
*Sent: *Friday, March 4, 2016 3:35:57 PM
*Subject: *Re: [Gluster-users] Per-client prefered server?
smime.p7s
Description: Signature cryptographique S/MIME
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
