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,
AnantGet Outlook for iOS
From: Hu Bert <revirii@xxxxxxxxxxxxxx>
Sent: Monday, February 5, 2024 6:15 PM
To: Anant Saraswat <anant.saraswat@xxxxxxxxxxxxxx>
Cc: gluster-users@xxxxxxxxxxx <gluster-users@xxxxxxxxxxx>
Subject: Re: Challenges with Replicated Gluster volume after stopping Gluster on any node.EXTERNAL: Do not click links or open attachments if you do not recognize the sender.
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.saraswat@xxxxxxxxxxxxxx>:
________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 shouldn't create any issues.
In our setup, when we stop Gluster on any of the nodes, we mostly get the error 'Transport endpoint is not connected' on the clients. When we run the commands to check the connected clients on the Gluster server, we get the following error:
gluster volume status tier1data clientsFAILED: Commit failed on master1. Error: Unable to decode brick op response.
Could anyone recommend a potential solution for this?
Thanks,Anant
Anant Saraswat
DevOps Lead
IT | Technology Blueprint Ltd.
+44-8450047142 (5020) | +91-9818761614
anant.saraswat@xxxxxxxxxxxxxx
https://www.technologyblueprint.co.uk
Salisbury House, Station Road, Cambridge, Cambridgeshire, CB1 2LA
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.
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 list
Gluster-users@xxxxxxxxxxx
https://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.
________ 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 list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
