<html><head></head><body><div class="ydp9caf0c40yahoo-style-wrap" style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Hi Ravi,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Can you clarify which script do you use ?</div><div dir="ltr" data-setdir="false">Usually I rely on oVirt to shutdown the system properly , but sometimes I have used '<span>/usr/share/glusterfs/scripts/stop-all-gluster-processes.sh' which kills everything (including fuse mounts).</span></div><div dir="ltr" data-setdir="false"><span><br></span></div><div dir="ltr" data-setdir="false"><span>Best Regards,</span></div><div dir="ltr" data-setdir="false"><span>Strahil Nikolov </span></div><div dir="ltr" data-setdir="false"><br></div><div><br></div>
</div><div id="ydpd92b6a5dyahoo_quoted_3795626740" class="ydpd92b6a5dyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
В вторник, 16 юли 2019 г., 17:32:44 ч. Гринуич+3, Gionatan Danti <g.danti@assyoma.it> написа:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On 16/07/2019 15:27, Ravishankar N wrote:<br></div><div dir="ltr">> Yes, if you simply pkill the gluster brick processes of the node before <br></div><div dir="ltr">> switching it off, you won't observe the hang on the clients because they <br></div><div dir="ltr">> will receive the disconnect notification immediately. But before that, <br></div><div dir="ltr">> you would need to check if there are no pending heals etc. You can use <br></div><div dir="ltr">> the script [1] which does all these checks in the graceful mode.<br></div><div dir="ltr"><br></div><div dir="ltr">Hi Ravi,<br></div><div dir="ltr">thanks for your reply. I tried killing the glusterfsd process and I <br></div><div dir="ltr">confirm that the client does not see any pause, indeed.<br></div><div dir="ltr"><br></div><div dir="ltr">I was thinking that during the shutdown procedure systemd would kill the <br></div><div dir="ltr">processes by itself; which it *does*, but only if the glusterfsd.service <br></div><div dir="ltr">is enabled/started.<br></div><div dir="ltr"><br></div><div dir="ltr">By default, the systemd service installed on CentOS 7 + Gluster 6.0 SIG <br></div><div dir="ltr">does not start glusterfsd.service and so, in the shutdown phase, it does <br></div><div dir="ltr">not stop it.<br></div><div dir="ltr"><br></div><div dir="ltr">Thanks very much for your information.<br></div><div dir="ltr"><br></div><div dir="ltr">-- <br></div><div dir="ltr">Danti Gionatan<br></div><div dir="ltr">Supporto Tecnico<br></div><div dir="ltr">Assyoma S.r.l. - www.assyoma.it<br></div><div dir="ltr">email: <a href="mailto:g.danti@assyoma.it" rel="nofollow" target="_blank">g.danti@assyoma.it</a> - <a href="mailto:info@assyoma.it" rel="nofollow" target="_blank">info@assyoma.it</a><br></div><div dir="ltr">GPG public key ID: FF5F32A8<br></div><div dir="ltr">_______________________________________________<br></div><div dir="ltr">Gluster-users mailing list<br></div><div dir="ltr"><a href="mailto:Gluster-users@gluster.org" rel="nofollow" target="_blank">Gluster-users@gluster.org</a><br></div><div dir="ltr"><a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="nofollow" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br></div></div>
</div>
</div></body></html>