[Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

Hello Everyone, We have a replicated Gluster volume with three nodes, and we face a strange issue whenever we need to restart one of the nodes in this cluster. As per my understanding, if we shut down one node, the Gluster mount should smoothly connect to another remaining Gluster server and

Re: [Gluster-users] Graceful shutdown doesn't stop all Gluster processes

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

Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

Hi, normally, when we shut down or reboot one of the (server) nodes, we call the "stop-all-gluster-processes.sh" script. But i think you did that, right? Best regards, Hubert Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat < anant.saras...@techblue.co.uk>: > Hello Everyone, > > We

[Gluster-users] Graceful shutdown doesn't stop all Gluster processes

Hello Everyone, I am using GlusterFS 9.4, and whenever we use the systemctl command to stop the Gluster server, it leaves many Gluster processes running. So, I just want to check how to shut down the Gluster server in a graceful manner. Is there any specific sequence or trick I need to

Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

Hi Hu, Yes, I have used the "stop-all-gluster-processes.sh" after systemctl stop. I consider "stop-all-gluster-processes.sh" as the last resort to kill all the remaining gluster processes. Do you use it primarily to stop the gluster? Thanks, Anant Get Outlook for iOS

Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.

Just a notice: bricks processes not being terminated prevents a simple "reboot" (or "shutdown -r now", or an automated shutdown initiated by UPS) to complete: you're left with most daemons (including sshd) terminated and a machine that's neither shutting down nor returning to normal operations