<div dir="ltr">Hello Gluster Community,<br><br><pre class="gmail-tw-data-text gmail-tw-ta gmail-tw-text-small" id="gmail-tw-target-text" style="text-align:left;height:408px"><span style="font-family:arial,helvetica,sans-serif"><span lang="en">I am using Gluster3.10 in a 2-Node-Szenario (with CentosOS7-machines). After restarting one of the nodes, <br>sometimes one of these two phenomena occurs:
1. The brick process of a volume on the newly started node is no longer running
2. The Brick Process Is Running But The First Knot Still Believes He Can not Reach <br> The Brick (Health info reported "Transport endpoint not connected")
In both cases it helps to stop and restart the volume (gluster volume stop, gluster volume start). <br>Sometimes you even have to do this twice! But this should be no soluton in a productive scenario. <br>For ealier releases there was a bug posted here: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1333711">https://bugzilla.redhat.com/show_bug.cgi?id=1333711</a><br>It seems to be that this bug is still an issue? Does anybody has some experience with that issue?<br><br>Regards<br><br>David Spisla<br></span></span></pre><pre class="gmail-tw-data-text gmail-tw-ta gmail-tw-text-small" id="gmail-tw-target-text" style="text-align:left;height:408px" dir="ltr"><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><br><br></span></span></pre></div>