Gluster users - Feb 2019 - Client failover question

I may have missed this in the documentation, but is there a way to make a
Gluster client server redundant? I have several bricks setup being
controlled by one cluster client server and if that server blows, there's
quite a bit of rebuilding to do. So looking for a way to ovoid that. Any
suggestions would be most appreciated.

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190208/93e3164b/attachment.html>

Hello,

What do you mean by a gluster 'client server' ?
A node is either a server (running the glusterd and glusterfsd/brick processes),
and you'd need at least 2 (3 is better, and the volume to be set as a
replica-3) or a gluster client (uses the gluster-client to mount a volume from a
gluster-cluster).
You could of-course also run the 'client' on the actual gluster-server
to mount to itself (wouldn't recommend that).

Nico

----- Oorspronkelijk bericht -----
Van: "Jim Laib" <jlaib01 at gmail.com>
Aan: "gluster-users" <gluster-users at gluster.org>
Verzonden: Vrijdag 8 februari 2019 17:04:45
Onderwerp: [Gluster-users] Client failover question

I may have missed this in the documentation, but is there a way to make a
Gluster client server redundant? I have several bricks setup being controlled by
one cluster client server and if that server blows, there's quite a bit of
rebuilding to do. So looking for a way to ovoid that. Any suggestions would be
most appreciated.

Thanks in advance. 

_______________________________________________ 
Gluster-users mailing list 
Gluster-users at gluster.org 
https://lists.gluster.org/mailman/listinfo/gluster-users