<div dir="ltr">glusterd should handle syncing any changes you make with the "gluster" command to the peers, obviously if you make local changes to the volume file on one server you are likely to break things unless you copy rsync the changes to the other server.</div><div class="gmail_extra"><br><div class="gmail_quote">On 22 September 2015 at 04:02, Andreas Hollaus <span dir="ltr"><<a href="mailto:Andreas.Hollaus@ericsson.com" target="_blank">Andreas.Hollaus@ericsson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Are there any restrictions as to when I'm allowed to make changes to the GlusterFS<br>
volume (for instance: start/stop volume, add/remove brick or peer)? How will it<br>
handle such changes when one of my two replicated servers is down? How will GlusterFS<br>
know which set of configuration files it can trust when the other server is connected<br>
again and the files will contain different information about the volume? If these<br>
were data files on the GlusterFS volume that would have been handled by the extended<br>
file attributes, but how about the GlusterFS configuration itself?<br>
<br>
Regards<br>
Andreas<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br></div>