On 17/07/19 8:50 PM, Strahil Nikolov wrote:
Hi Ravi,
Can you clarify which script do you use ?
Usually I rely on oVirt to shutdown the system properly , but
sometimes I have used
'/usr/share/glusterfs/scripts/stop-all-gluster-processes.sh' which
kills everything (including fuse mounts).
This is the same script I referred to in my reply
(https://github.com/gluster/glusterfs/blob/master/extras/stop-all-gluster-processes.sh)
. Not sure why the email is not delivered to the mailing list.
Regards,
Ravi
Best Regards,
Strahil Nikolov
В вторник, 16 юли 2019 г., 17:32:44 ч. Гринуич+3, Gionatan Danti
<[email protected]> написа:
On 16/07/2019 15:27, Ravishankar N wrote:
> Yes, if you simply pkill the gluster brick processes of the node before
> switching it off, you won't observe the hang on the clients because
they
> will receive the disconnect notification immediately. But before that,
> you would need to check if there are no pending heals etc. You can use
> the script [1] which does all these checks in the graceful mode.
Hi Ravi,
thanks for your reply. I tried killing the glusterfsd process and I
confirm that the client does not see any pause, indeed.
I was thinking that during the shutdown procedure systemd would kill the
processes by itself; which it *does*, but only if the glusterfsd.service
is enabled/started.
By default, the systemd service installed on CentOS 7 + Gluster 6.0 SIG
does not start glusterfsd.service and so, in the shutdown phase, it does
not stop it.
Thanks very much for your information.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: [email protected] <mailto:[email protected]> -
[email protected] <mailto:[email protected]>
GPG public key ID: FF5F32A8
_______________________________________________
Gluster-users mailing list
[email protected] <mailto:[email protected]>
https://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
https://lists.gluster.org/mailman/listinfo/gluster-users
