Gluster users - Feb 2024 - Graceful shutdown doesn't stop all Gluster processes

Hi Strahil,

Yes, we mount the fuse to the physical host and then use bind mount to provide
access to the container.

The same physical host also runs the gluster server. Therefore, when we stop
gluster using 'stop-all-gluster-processes.sh' on the physical host, it
kills the fuse mount and impacts containers accessing this volume via bind.

Thanks,
Anant

________________________________
From: Strahil Nikolov <hunter86_bg at yahoo.com>
Sent: 16 February 2024 3:51 PM
To: Anant Saraswat <anant.saraswat at techblue.co.uk>; Aravinda
<aravinda at kadalu.tech>
Cc: ronny.adsetts at amazinginternet.com <ronny.adsetts at
amazinginternet.com>; gluster-users at gluster.org <gluster-users at
gluster.org>
Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes


EXTERNAL: Do not click links or open attachments if you do not recognize the
sender.

Hi Anant,

Do you use the fuse client in the container ?
Wouldn't it be more reasonable to mount the fuse and then use bind mount to
provide access to the container ?

Best Regards,
Strahil Nikolov

On Fri, Feb 16, 2024 at 15:02, Anant Saraswat
<anant.saraswat at techblue.co.uk> wrote:
Okay, I understand. Yes, it would be beneficial to include an option for
skipping the client processes. This way, we could utilize the
'stop-all-gluster-processes.sh' script with that option to stop the
gluster server process while retaining the fuse mounts.

________________________________
From: Aravinda <aravinda at kadalu.tech>
Sent: 16 February 2024 12:36 PM
To: Anant Saraswat <anant.saraswat at techblue.co.uk>
Cc: ronny.adsetts at amazinginternet.com <ronny.adsetts at
amazinginternet.com>; gluster-users at gluster.org <gluster-users at
gluster.org>; Strahil Nikolov <hunter86_bg at yahoo.com>
Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes


EXTERNAL: Do not click links or open attachments if you do not recognize the
sender.

No. If the script is used to update the GlusterFS packages in the node, then we
need to stop the client processes as well (Fuse client is `glusterfs` process.
`ps ax | grep glusterfs`).

The default behaviour can't be changed, but the script can be enhanced by
adding a new option `--skip-clients` so that it can skip stopping the client
processes.

--
Aravinda
Kadalu Technologies



---- On Fri, 16 Feb 2024 16:15:22 +0530 Anant Saraswat <anant.saraswat at
techblue.co.uk> wrote ---

Hello Everyone,

We are mounting this external Gluster volume (dc.local:/docker_config) for
docker configuration on one of the Gluster servers. When I ran the
stop-all-gluster-processes.sh script, I wanted to stop all gluster
server-related processes on the server, but not to unmount the external gluster
volume mounted on the server. However, running stop-all-gluster-processes.sh
unmounted the dc.local:/docker_config volume from the server.

/dev/mapper/tier1data                   6.1T  4.7T  1.4T  78%
/opt/tier1data/brick
dc.local:/docker_config  100G   81G   19G  82% /opt/docker_config

Do you think stop-all-gluster-processes.sh should unmount the fuse mount?

Thanks,
Anant
________________________________
From: Gluster-users <gluster-users-bounces at
gluster.org<mailto:gluster-users-bounces at gluster.org>> on behalf of
Strahil Nikolov <hunter86_bg at yahoo.com<mailto:hunter86_bg at
yahoo.com>>
Sent: 09 February 2024 5:23 AM
To: ronny.adsetts at amazinginternet.com<mailto:ronny.adsetts at
amazinginternet.com> <ronny.adsetts at
amazinginternet.com<mailto:ronny.adsetts at amazinginternet.com>>;
gluster-users at gluster.org<mailto:gluster-users at gluster.org>
<gluster-users at gluster.org<mailto:gluster-users at gluster.org>>
Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes


EXTERNAL: Do not click links or open attachments if you do not recognize the
sender.

I think the service that shutdowns the bricks on EL systems is something like
this - right now I don't have access to my systems to check but you can
extract the rpms and see it:

https://bugzilla.redhat.com/show_bug.cgi?id=1022542#c4<https://urldefense.com/v3/__https://bugzilla.redhat.com/show_bug.cgi?id=1022542*c4__;Iw!!I_DbfM1H!ANXDSlATEqmc-hZeQJEeNr5LKu6Z4rpDBonAviThOtduuz84ZfDwxEkQHcrf6CFS8dpRpb0zbRYgH6UMwahQLv5u9f4cAQ$>

Best Regards,
Strahil Nikolov

On Wed, Feb 7, 2024 at 19:51, Ronny Adsetts
<ronny.adsetts at amazinginternet.com<mailto:ronny.adsetts at
amazinginternet.com>> wrote:
________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge:
https://meet.google.com/cpu-eiue-hvk<https://urldefense.com/v3/__https://meet.google.com/cpu-eiue-hvk__;!!I_DbfM1H!ANXDSlATEqmc-hZeQJEeNr5LKu6Z4rpDBonAviThOtduuz84ZfDwxEkQHcrf6CFS8dpRpb0zbRYgH6UMwahQLv47B8Cc5w$>
Gluster-users mailing list
Gluster-users at gluster.org<mailto:Gluster-users at gluster.org>
https://lists.gluster.org/mailman/listinfo/gluster-users<https://urldefense.com/v3/__https://lists.gluster.org/mailman/listinfo/gluster-users__;!!I_DbfM1H!ANXDSlATEqmc-hZeQJEeNr5LKu6Z4rpDBonAviThOtduuz84ZfDwxEkQHcrf6CFS8dpRpb0zbRYgH6UMwahQLv4J669uHw$>


DISCLAIMER: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify the sender.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender immediately
by email if you have received this email by mistake and delete this email from
your system.

If you are not the intended recipient, you are notified that disclosing,
copying, distributing or taking any action in reliance on the contents of this
information is strictly prohibited. Thanks for your cooperation.



DISCLAIMER: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify the sender.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender immediately
by email if you have received this email by mistake and delete this email from
your system.

If you are not the intended recipient, you are notified that disclosing,
copying, distributing or taking any action in reliance on the contents of this
information is strictly prohibited. Thanks for your cooperation.

DISCLAIMER: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify the sender.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender immediately
by email if you have received this email by mistake and delete this email from
your system.

If you are not the intended recipient, you are notified that disclosing,
copying, distributing or taking any action in reliance on the contents of this
information is strictly prohibited. Thanks for your cooperation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20240216/a92ba73b/attachment.html>

Well,

you prepare the host for shutdown, right ? So why don't you setup systemd to
start the container and shut it down before the bricks ?

Best Regards,
Strahil Nikolov






? ?????, 16 ???????? 2024 ?. ? 18:48:36 ?. ???????+2, Anant Saraswat
<anant.saraswat at techblue.co.uk> ??????:







Hi Strahil,



Yes, we mount the fuse to the physical host and then use bind mount to provide
access to the container.



The same physical host also runs the gluster server. Therefore, when we stop
gluster using 'stop-all-gluster-processes.sh' on the physical host, it
kills the fuse mount and impacts containers accessing this volume via bind.



Thanks,

Anant



________________________________ 
From:?Strahil Nikolov <hunter86_bg at yahoo.com>
Sent:?16 February 2024 3:51 PM
To:?Anant Saraswat <anant.saraswat at techblue.co.uk>; Aravinda
<aravinda at kadalu.tech>
Cc:?ronny.adsetts at amazinginternet.com <ronny.adsetts at
amazinginternet.com>; gluster-users at gluster.org <gluster-users at
gluster.org>
Subject:?Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes
?


EXTERNAL:?Do not click links or open attachments if you do not recognize the
sender.

Hi Anant,



Do you use the fuse client in the container ? 
Wouldn't it be more reasonable to mount the fuse and then use bind mount to
provide access to the container ?




Best Regards,

Strahil Nikolov



>??
> On Fri, Feb 16, 2024 at 15:02, Anant Saraswat
> 
> <anant.saraswat at techblue.co.uk> wrote:
> 
>??
>??
> Okay, I understand. Yes, it would be beneficial to include an option for
skipping the client processes. This way, we could utilize the
'stop-all-gluster-processes.sh' script with that option to stop the
gluster server process while retaining the fuse mounts.
> 
> 
> 
>??
> 
> ________________________________ 
>??
> From:?Aravinda <aravinda at kadalu.tech>
> Sent:?16 February 2024 12:36 PM
> To:?Anant Saraswat <anant.saraswat at techblue.co.uk>
> Cc:?ronny.adsetts at amazinginternet.com <ronny.adsetts at
amazinginternet.com>; gluster-users at gluster.org <gluster-users at
gluster.org>; Strahil Nikolov <hunter86_bg at yahoo.com>
> Subject:?Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes
> ?
> 
> 
> EXTERNAL:?Do not click links or open attachments if you do not recognize
the sender.
> 
> No. If the script is used to update the GlusterFS packages in the node,
then we need to stop the client processes as well (Fuse client is `glusterfs`
process. `ps ax | grep glusterfs`).
> 
> 
> 
> The default behaviour can't be changed, but the script can be enhanced
by adding a new option `--skip-clients` so that it can skip stopping the client
processes.
> 
> 
> 
> --
> 
>??
> Aravinda
> 
> Kadalu Technologies
> 
> 
> 
> 
>??
> 
> 
> 
> ---- On Fri, 16 Feb 2024 16:15:22 +0530??Anant Saraswat <anant.saraswat
at techblue.co.uk>?wrote ---
> 
> 
> 
> 
>??Hello Everyone,
> 
>??
> 
> 
> We are mounting this external Gluster volume (dc.local:/docker_config) for
docker configuration on one of the Gluster servers. When I ran the
stop-all-gluster-processes.sh script, I wanted to stop all gluster
server-related processes on the server, but not to unmount the external gluster
volume mounted on the server. However, running stop-all-gluster-processes.sh
unmounted the dc.local:/docker_config volume from the server.
> 
> 
> 
> /dev/mapper/tier1data ? ? ? ? ? ? ? ? ? 6.1T ?4.7T ?1.4T ?78%
/opt/tier1data/brick
> 
> dc.local:/docker_config ?100G ? 81G ? 19G ?82% /opt/docker_config
> 
> 
> 
> Do you think stop-all-gluster-processes.sh should unmount the fuse mount?
> 
> 
> 
> Thanks,
> 
> Anant
> ________________________________ 
> From:?Gluster-users <gluster-users-bounces at gluster.org> on behalf
of Strahil Nikolov <hunter86_bg at yahoo.com>
> Sent:?09 February 2024 5:23 AM
> To:?ronny.adsetts at amazinginternet.com?<ronny.adsetts at
amazinginternet.com>;??gluster-users at gluster.org?<gluster-users at
gluster.org>
> Subject:?Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes
> ?
> 
> 
> EXTERNAL:?Do not click links or open attachments if you do not recognize
the sender.
> 
> I think the service that shutdowns the bricks on EL systems is something
like this - right now I don't have access to my systems to check but you can
extract the rpms and see it:
> 
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1022542#c4
> 
> 
> 
> Best Regards,
> 
> Strahil Nikolov
> 
>>??
>> On Wed, Feb 7, 2024 at 19:51, Ronny Adsetts
>> 
>> <ronny.adsetts at amazinginternet.com> wrote:
>> 
>>??________Community Meeting Calendar:Schedule -Every 2nd and 4th Tuesday
at 14:30 IST / 09:00
UTCBridge:??https://meet.google.com/cpu-eiue-hvkGluster-users mailing
listGluster-users at
gluster.orghttps://lists.gluster.org/mailman/listinfo/gluster-users
>> 
> 
> 
> 
> DISCLAIMER: This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify the sender.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender immediately
by email if you have received this email by mistake and delete this email from
your system.If you are not the intended recipient, you are notified that
disclosing, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited. Thanks for your
cooperation.
> 
>??
> 
> 
> 
> 
> 
> DISCLAIMER: This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify the sender.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender immediately
by email if you have received this email by mistake and delete this email from
your system.
> 
> If you are not the intended recipient, you are notified that disclosing,
copying, distributing or taking any action in reliance on the contents of this
information is strictly prohibited. Thanks for your cooperation.
> 
>??
>??


DISCLAIMER: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify the sender.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender immediately
by email if you have received this email by mistake and delete this email from
your system.

If you are not the intended recipient, you are notified that disclosing,
copying, distributing or taking any action in reliance on the contents of this
information is strictly prohibited. Thanks for your cooperation.