me know if this process can be optimized, I will be happy to do so.
Many thanks,Anant
From: Strahil Nikolov
Sent: 24 February 2024 12:33 PM
To: Anant Saraswat
Cc: gluster-users@gluster.org
Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes EXTERNAL: Do not click
-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,
why would you need to shutdown a brick to expand it ? This is an online
operation.
Best Regards,
Strahil Nikolov
DISCLAIMER: This email
Hi Anant,
why would you need to shutdown a brick to expand it ? This is an online
operation.
Best Regards,
Strahil Nikolov
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing
ailto:hunter86...@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
; Anant Saraswat
Cc: ronny.adse...@amazinginternet.com ;
gluster-users@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.
Well,
you prepare the host for shutdown
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
>
> Fro
ilto:ronny.adse...@amazinginternet.com>
mailto:ronny.adse...@amazinginternet.com>>;
gluster-users@gluster.org<mailto:gluster-users@gluster.org>
mailto:gluster-users@gluster.org>>
Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes
EXTERNAL: Do not cl
: ronny.adse...@amazinginternet.com ;
gluster-users@gluster.org ; Strahil Nikolov
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
.
From: Aravinda
Sent: 16 February 2024 12:36 PM
To: Anant Saraswat
Cc: ronny.adse...@amazinginternet.com ;
gluster-users@gluster.org ; Strahil Nikolov
Subject: Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster
processes
EXTERNAL: Do not click links or open attachments if you do
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 h
-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
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
If I might chip in here, this can cause an issue when rebooting nodes unless
you make sure to stop the Gluster processes first. If you don't stop the
processes, then the Gluster volumes can pause for the default 42 seconds(?)
until the other nodes time out the rebooting node. This is of course
Hi Anant,
It was intentional design decision to not stop any gluster processes if
Glusterd need to be upgraded or if Glusterd crashes. Because of this Volume
availability will not be affected if any issues with Glusterd or Glusterd is
upgraded. All the mounts will reconnect once the Glusterd
14 matches
Mail list logo
