<div dir="ltr">Glusterfs needs quorum, so if you have two servers and one goes down, there is no quorum, so all writes stop until the server comes back up. You can add a third server as an arbiter which does not store data in the bricks, but still uses some minimal space (to keep metadata for the files).<div><br></div><div>HTH,</div><div><br></div><div>DIego</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 23, 2019 at 3:06 PM Gilberto Nunes <<a href="mailto:gilberto.nunes32@gmail.com">gilberto.nunes32@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hit there...<div><br></div><div>I have set up two server as replica, like this:</div><div><br></div><div>gluster vol create Vol01 server1:/data/storage server2:/data/storage</div><div><br></div><div>Then I create a config file in client, like this:</div><div><div>volume remote1</div><div> type protocol/client</div><div> option transport-type tcp</div><div> option remote-host server1</div><div> option remote-subvolume /data/storage</div><div> end-volume</div><div><br></div><div> volume remote2</div><div> type protocol/client</div><div> option transport-type tcp</div><div> option remote-host server2</div><div> option remote-subvolume /data/storage</div><div> end-volume</div><div><br></div><div> volume replicate<br></div><div> type cluster/replicate</div><div> subvolumes remote1 remote2</div><div> end-volume</div><div><br></div><div> volume writebehind</div><div> type performance/write-behind</div><div> option window-size 1MB</div><div> subvolumes replicate</div><div> end-volume</div><div><br></div><div> volume cache</div><div> type performance/io-cache</div><div> option cache-size 512MB</div><div> subvolumes writebehind</div><div> end-volume</div></div><div><br></div><div>And add this line in /etc/fstab</div><div><br></div><div>/etc/glusterfs/datastore.vol /mnt glusterfs defaults,_netdev 0 0<br></div><div><br></div><div>After mount /mnt, I can access the servers. So far so good!</div><div>But when I make server1 crash, I was unable to access /mnt or even use </div><div>gluster vol status</div><div>on server2</div><div><br></div><div>Everything hangon!</div><div><br></div><div>I have tried with replicated, distributed and replicated-distributed too.</div><div>I am using Debian Stretch, with gluster package installed via apt, provided by Standard Debian Repo, glusterfs-server 3.8.8-1</div><div><br></div><div>I am sorry if this is a newbie question, but glusterfs share it's not suppose to keep online if one server goes down?</div><div><br></div><div>Any adviced will be welcome</div><div><br></div><div>Best</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br class="gmail-m_-1894462702772612631gmail-Apple-interchange-newline"><div><div dir="ltr" class="gmail-m_-1894462702772612631gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>---</div><div><div><div>Gilberto Nunes Ferreira</div></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">(47) 3025-5907</span><br></div><div><font size="4"><b></b></font></div><div><span style="font-size:12.8px">(47) 99676-7530 - Whatsapp / Telegram</span><br></div><div><p style="font-size:12.8px;margin:0px"></p><p style="font-size:12.8px;margin:0px">Skype: gilberto.nunes36</p><p style="font-size:12.8px;margin:0px"><br></p></div></div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>