IIUC, you would essentially be unmounting the volume from the old building and mounting it near the new building, correct?
In that case, you would need to set the read-subvolume-index command line option appropriately when mounting again.
The selection of the new read child will not happen automatically.
HTH,In that case, you would need to set the read-subvolume-index command line option appropriately when mounting again.
The selection of the new read child will not happen automatically.
On Fri, Mar 4, 2016 at 5:59 PM, Yannick Perret <yannick.perret@xxxxxxxxxxxxx> wrote:
Le 04/03/2016 13:12, Krutika Dhananjay a écrit :
Thanks for that tip!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>
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.perret@xxxxxxxxxxxxx>
To: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx>
Cc: gluster-users@xxxxxxxxxxx
Sent: Friday, March 4, 2016 3:35:57 PM
Subject: Re: Per-client prefered server?
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
