<div dir="ltr">Let's go with the data collection first.<div><br></div><div>What linux distro ? </div><div><br></div><div>Anything special about your network configuration ? </div><div><br></div><div>Any chance your server is taking too long to release networking and gluster is starting before network is ready ?</div>
<div><br></div><div>Can you completely disable iptables and test again ? </div><div><br></div><div>I am afraid quorum will not help you if you cannot get this issue corrected. </div><div><br></div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Mar 25, 2014 at 3:14 PM, Артём Конвалюк <span dir="ltr"><<a href="mailto:artret@gmail.com" target="_blank">artret@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hello!<br><br>I have 2 nodes with GlusterFS 3.4.2. I created one replica volume using 2 bricks and enabled glusterd autostarts. Also firewall is configured and I have to run "iptables -F" on nodes after reboot. It is clear that firewall should be disabled in LAN, but I'm interested in my case.<br>
<br>Problem: When I reboot both nodes and run "iptables -F" peer status is still disconnected. I wonder why. After "service glusterd restart" peer status is connected. But I have to run "gluster volume heal <volume-name>" to make both servers consistent and be able to replicate files. Is there any way to eliminate this problem?<br>
<br>I read about server-quorum, but it needs 3 or more nodes. Am I right?<br><br>Best Regards,<br>Artem Konvalyuk</div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>