<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On 22-Mar-2016 6:54 pm, "<a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a>" <<a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a>> wrote:<br>
><br>
> Hi Atin,<br>
><br>
> Setting 'state=3' on the instances and restarting the service seems to have fixed the problem.</p>
<p dir="ltr">Great!</p>
<p dir="ltr">><br>
> Is this an 'issue' with glusterfs?</p>
<p dir="ltr">No, its not. As I said the handshaking was incomplete which lead to this issue. I'd also recommend you to upgrade to latest gluster version i.e. 3.7.x?</p>
<p dir="ltr">><br>
> I will implement an automated solution for my problem, just would be good to know if this is something that will be patched in the future?<br>
><br>
> Thanks,<br>
> Tommy<br>
><br>
> -----Original Message-----<br>
> From: Atin Mukherjee [mailto:<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>]<br>
> Sent: 22 March 2016 13:10<br>
> To: Yardley, Tommy (UK Guildford); <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Subject: Re: [Gluster-users] GlusterFS cluster peer stuck in state: Sent and Received peer request (Connected)<br>
><br>
> Tommy,<br>
><br>
> It seems like that there were frequent disconnect events which may have caused the peer handshaking to remain incomplete and leading to an inconsistency in the cluster state.<br>
><br>
> Further follow up questions:<br>
><br>
> 1. Restarting glusterd instances doesn't solve the problem?<br>
><br>
> 2. If answer to 1 is yes can we try to set state=3 in all the /var/lib/glusterd/peers/<UUID> files and then restart glusterd to see whether the problem persists?<br>
><br>
> If the above still doesn't solve the problem output of 'cat /var/lib/glusterd/peers/*' from all the nodes should help us in figuring out the correct workaround.<br>
><br>
> ~Atin<br>
><br>
> On 03/22/2016 02:51 PM, Atin Mukherjee wrote:<br>
> > Gaurav is looking into it and he will get back with his analysis.<br>
> ><br>
> > ~Atin<br>
> ><br>
> > On 03/22/2016 02:42 PM, <a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a> wrote:<br>
> >> Hi,<br>
> >><br>
> >> Is anyone able to help with this issue?<br>
> >><br>
> >> Thanks,<br>
> >> Tommy<br>
> >><br>
> >> -----Original Message-----<br>
> >> From: <a href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a><br>
> >> [mailto:<a href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a>] On Behalf Of<br>
> >> <a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a><br>
> >> Sent: 17 March 2016 08:49<br>
> >> To: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> >> Subject: Re: [Gluster-users] GlusterFS cluster peer stuck in state:<br>
> >> Sent and Received peer request (Connected)<br>
> >><br>
> >> Hi,<br>
> >><br>
> >> Sorry I had sent them directly to Atin<br>
> >><br>
> >> I've trimmed down the larger log files a bit and attached all of them to this email.<br>
> >><br>
> >> Many thanks,<br>
> >> Tommy<br>
> >><br>
> >> -----Original Message-----<br>
> >> From: Gaurav Garg [mailto:<a href="mailto:ggarg@redhat.com">ggarg@redhat.com</a>]<br>
> >> Sent: 17 March 2016 07:07<br>
> >> To: Yardley, Tommy (UK Guildford)<br>
> >> Cc: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> >> Subject: Re: [Gluster-users] GlusterFS cluster peer stuck in state:<br>
> >> Sent and Received peer request (Connected)<br>
> >><br>
> >>>>> I’ve sent the logs directly as they push this message over the size limit.<br>
> >><br>
> >> Where have you send logs. i could not able to find. could you send glusterd logs so that we can start analyzing this issue.<br>
> >><br>
> >> Thanks,<br>
> >><br>
> >> Regards,<br>
> >> Gaurav<br>
> >><br>
> >> ----- Original Message -----<br>
> >> From: "Atin Mukherjee" <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>><br>
> >> To: "tommy yardley" <<a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a>>,<br>
> >> <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> >> Sent: Wednesday, March 16, 2016 5:49:05 PM<br>
> >> Subject: Re: [Gluster-users] GlusterFS cluster peer stuck in state:<br>
> >> Sent and Received peer request (Connected)<br>
> >><br>
> >> I couldn't look into this today, sorry about that. I can only look into this case on Monday. Anyone else to take this up?<br>
> >><br>
> >> ~Atin<br>
> >><br>
> >> On 03/15/2016 09:57 PM, <a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a> wrote:<br>
> >>> Hi Atin,<br>
> >>><br>
> >>><br>
> >>><br>
> >>> All nodes are running 3.5.8 – the probe sequence is:<br>
> >>> 172.31.30.64<br>
> >>><br>
> >>> 172.31.27.27 (node having issue)<br>
> >>><br>
> >>> 172.31.26.134 (node the peer probe is ran on)<br>
> >>><br>
> >>> 172.31.19.46<br>
> >>><br>
> >>><br>
> >>><br>
> >>> I’ve sent the logs directly as they push this message over the size limit.<br>
> >>><br>
> >>><br>
> >>><br>
> >>> look forward to your reply,<br>
> >>><br>
> >>><br>
> >>><br>
> >>> Tommy<br>
> >>><br>
> >>><br>
> >>><br>
> >>><br>
> >>><br>
> >>> *From:*Atin Mukherjee [mailto:<a href="mailto:atin.mukherjee83@gmail.com">atin.mukherjee83@gmail.com</a>]<br>
> >>> *Sent:* 15 March 2016 15:58<br>
> >>> *To:* Yardley, Tommy (UK Guildford)<br>
> >>> *Cc:* <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> >>> *Subject:* Re: [Gluster-users] GlusterFS cluster peer stuck in state:<br>
> >>> Sent and Received peer request (Connected)<br>
> >>><br>
> >>><br>
> >>><br>
> >>> This indicates the peer handshaking didn't go through properly and<br>
> >>> your cluster is messed up. Are you running 3.5.8 version in all the nodes?<br>
> >>> Could you get me the glusterd log from all the nodes and mention the<br>
> >>> peer probe sequence? I'd be able to look at it tomorrow only and get back.<br>
> >>><br>
> >>> -Atin<br>
> >>> Sent from one plus one<br>
> >>><br>
> >>> On 15-Mar-2016 9:16 pm, "<a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a><br>
> >>> <mailto:<a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a>>" <<a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a><br>
> >>> <mailto:<a href="mailto:tommy.yardley@baesystems.com">tommy.yardley@baesystems.com</a>>> wrote:<br>
> >>><br>
> >>> Hi All,<br>
> >>><br>
> >>><br>
> >>><br>
> >>> I’m running GlusterFS on a cluster hosted in AWS. I have a script<br>
> >>> which provisions my instances and thus will set up GlusterFS (specifically:<br>
> >>> glusterfs 3.5.8).<br>
> >>><br>
> >>> My issue is that this only works ~50% of the time and the other 50%<br>
> >>> of the time one of the peers will be ‘stuck’ in the following state:<br>
> >>><br>
> >>> /root@ip-xx-xx-xx-1:/home/ubuntu# gluster peer status/<br>
> >>><br>
> >>> /Number of Peers: 3/<br>
> >>><br>
> >>> / /<br>
> >>><br>
> >>> /Hostname: xx.xx.xx.2/<br>
> >>><br>
> >>> /Uuid: 3b4c1fb9-b325-4204-98fd-2eb739fa867f/<br>
> >>><br>
> >>> /State: Peer in Cluster (Connected)/<br>
> >>><br>
> >>> / /<br>
> >>><br>
> >>> /Hostname: xx.xx.xx.3/<br>
> >>><br>
> >>> /Uuid: acfc1794-9080-4eb0-8f69-3abe78bbee16/<br>
> >>><br>
> >>> /State: Sent and Received peer request (Connected)/<br>
> >>><br>
> >>> / /<br>
> >>><br>
> >>> /Hostname: xx.xx.xx.4/<br>
> >>><br>
> >>> /Uuid: af33463d-1b32-4ffb-a4f0-46ce16151e2f/<br>
> >>><br>
> >>> /State: Peer in Cluster (Connected)/<br>
> >>><br>
> >>><br>
> >>><br>
> >>> Running gluster peer status on the instance that is affected yields:<br>
> >>><br>
> >>><br>
> >>><br>
> >>> /root@ip-xx-xx-xx-3:/var/log/glusterfs# gluster peer status Number<br>
> >>> of<br>
> >>> Peers: 1/<br>
> >>><br>
> >>> / /<br>
> >>><br>
> >>> /Hostname: xx.xx.xx.1/<br>
> >>><br>
> >>> /Uuid: c4f17e9a-893b-48f0-a014-1a05cca09d01/<br>
> >>><br>
> >>> /State: Peer is connected and Accepted (Connected)/<br>
> >>><br>
> >>> / /<br>
> >>><br>
> >>> Of which the status (Connected) in this case, will fluctuate between<br>
> >>> ‘Connected’ and ‘Disconnected’.<br>
> >>><br>
> >>><br>
> >>><br>
> >>> I have been unable to locate the cause of this issue. Has this been<br>
> >>> encountered before, and if so is there a general fix? I haven’t been<br>
> >>> able to find anything as of yet.<br>
> >>><br>
> >>><br>
> >>><br>
> >>> Many thanks,<br>
> >>><br>
> >>><br>
> >>><br>
> >>> *Tommy*<br>
> >>><br>
> >>><br>
> >>><br>
> >>> Please consider the environment before printing this email. This<br>
> >>> message should be regarded as confidential. If you have received<br>
> >>> this email in error please notify the sender and destroy it immediately.<br>
> >>> Statements of intent shall only become binding when confirmed in<br>
> >>> hard copy by an authorised signatory. The contents of this email may<br>
> >>> relate to dealings with other companies under the control of BAE<br>
> >>> Systems Applied Intelligence Limited, details of which can be found<br>
> >>> at <a href="http://www.baesystems.com/Businesses/index.htm">http://www.baesystems.com/Businesses/index.htm</a>.<br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> Gluster-users mailing list<br>
> >>> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>><br>
> >>> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> >>><br>
> >>> Please consider the environment before printing this email. This<br>
> >>> message should be regarded as confidential. If you have received<br>
> >>> this email in error please notify the sender and destroy it immediately.<br>
> >>> Statements of intent shall only become binding when confirmed in<br>
> >>> hard copy by an authorised signatory. The contents of this email may<br>
> >>> relate to dealings with other companies under the control of BAE<br>
> >>> Systems Applied Intelligence Limited, details of which can be found<br>
> >>> at <a href="http://www.baesystems.com/Businesses/index.htm">http://www.baesystems.com/Businesses/index.htm</a>.<br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> Gluster-users mailing list<br>
> >>> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> >>> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> >>><br>
> >> _______________________________________________<br>
> >> Gluster-users mailing list<br>
> >> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> >> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> >> Please consider the environment before printing this email. This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies under the control of BAE Systems Applied Intelligence Limited, details of which can be found at <a href="http://www.baesystems.com/Businesses/index.htm">http://www.baesystems.com/Businesses/index.htm</a>.<br>
> >> Please consider the environment before printing this email. This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies under the control of BAE Systems Applied Intelligence Limited, details of which can be found at <a href="http://www.baesystems.com/Businesses/index.htm">http://www.baesystems.com/Businesses/index.htm</a>.<br>
> >> _______________________________________________<br>
> >> Gluster-users mailing list<br>
> >> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> >> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> >><br>
> > _______________________________________________<br>
> > Gluster-users mailing list<br>
> > <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
> ><br>
> Please consider the environment before printing this email. This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies under the control of BAE Systems Applied Intelligence Limited, details of which can be found at <a href="http://www.baesystems.com/Businesses/index.htm">http://www.baesystems.com/Businesses/index.htm</a>.<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></p>