Got it. Thanks so much!
On Tue, Jun 24, 2014 at 11:28 AM, JuanFra Rodriguez Cardoso <juanfra.rodriguez.cardoso@xxxxxxxxx> wrote:
Hi Ryan:Example:
You may use the 'backupvolfile-server' option while mounting. According to RHS documentation:
backupvolfile-server=server name - name of the backup volfile server to mount the client. If this option is added while mounting fuse client, when the first volfile server fails, then the server specified in backupvolfile-server option is used as volfile server to mount the client.
# mount -t glusterfs -o backupvolfile-server=volfile_server2,fetch-attempts=2,log-level=WARNING,log-file=/var/log/gluster.log server1:/test-volume /mnt/glusterfsRegards,---
JuanFra Rodríguez Cardoso2014-06-24 18:19 GMT+02:00 Ryan Nix <ryan.nix@xxxxxxxxx>:_______________________________________________Hello,I recently put a very basic Gluster replication together (2 replicas) and mounted the volume on another server using the Gluster client. However, I was wondering if the 3.5 Gluster client knows about the other replicated volume. In other words, if one of the servers goes down, will the Gluster client know about the replicated volume and keep working?I saw this posting http://www.gluster.org/category/failover/ and it seems that was proposed to replace something like RRDNS but it was unclear if that feature made its way into one more the more recent builds.
Thanks!Ryan
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
