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

Hu Bert revirii at googlemail.com
Wed Feb 7 06:55:15 UTC 2024


Hi Anant,
e.g. if i reboot a gluster server this is the only script that i use - i
don't use systemctl at all.

Best regards,
Hubert


Am Mo., 5. Feb. 2024 um 19:22 Uhr schrieb Anant Saraswat <
anant.saraswat at techblue.co.uk>:

> 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 <https://aka.ms/o0ukef>
> ------------------------------
> *From:* Hu Bert <revirii at googlemail.com>
> *Sent:* Monday, February 5, 2024 6:15 PM
> *To:* Anant Saraswat <anant.saraswat at techblue.co.uk>
> *Cc:* gluster-users at gluster.org <gluster-users at gluster.org>
> *Subject:* Re: [Gluster-users] 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 at techblue.co.uk>:
>
>> 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 clients
>> FAILED: 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.
>> [image: mobilePhone]
>> +44-8450047142 (5020) <+44-8450047142%20(5020)> | +91-9818761614
>>
>> [image: emailAddress]
>> anant.saraswat at techblue.co.uk
>>
>> [image: website]
>> https://www.technologyblueprint.co.uk
>> <https://urldefense.com/v3/__https://www.technologyblueprint.co.uk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4EZVhUf-$>
>>
>> [image: address]
>> 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
>> <https://urldefense.com/v3/__https://meet.google.com/cpu-eiue-hvk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4BWhreAq$>
>> Gluster-users mailing list
>> 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!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4IQKpS1U$>
>>
> 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/20240207/211f104d/attachment.html>


More information about the Gluster-users mailing list