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.perret at
liris.cnrs.fr>
> *To: *"Krutika Dhananjay" <kdhananj at redhat.com>
> *Cc: *gluster-users at gluster.org
> *Sent: *Friday, March 4, 2016 3:35:57 PM
> *Subject: *Re: [Gluster-users] Per-client prefered server?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160304/c160b09a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3369 bytes
Desc: Signature cryptographique S/MIME
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160304/c160b09a/attachment.p7s>