search for: goossens

On Sat, 28 Oct 2017 at 02:36, Jo Goossens <jo.goossens at hosted-power.com> wrote: > Hello Atin, > > > > > > I just read it and very happy you found the issue. We really hope this > will be fixed in the next 3.10.7 version! > 3.10.7 - no I guess as the patch is still in review and 3.10.7 is getting tagged...

...ses? We kept 3.10 and hope to stay stable :/ Regards Jo ? ? -----Original message----- From:Atin Mukherjee <amukherj at redhat.com> Sent:Tue 23-01-2018 05:15 Subject:Re: [Gluster-users] BUG: After stop and start wrong port is advertised To:Alan Orth <alan.orth at gmail.com>; CC:Jo Goossens <jo.goossens at hosted-power.com>; gluster-users at gluster.org; So from the logs what it looks to be a regression caused by commit 635c1c3 ( and the good news is that this is now fixed in release-3.12 branch and should be part of 3.12.5. ?Commit which fixes this issue: COMMIT: https://...

...ould you confirm this should have been fixed in 3.10.8? If so we'll test it for sure! Regards Jo ? ? -----Original message----- From:Atin Mukherjee <amukherj at redhat.com> Sent:Mon 30-10-2017 17:40 Subject:Re: [Gluster-users] BUG: After stop and start wrong port is advertised To:Jo Goossens <jo.goossens at hosted-power.com>; CC:gluster-users at gluster.org; On Sat, 28 Oct 2017 at 02:36, Jo Goossens <jo.goossens at hosted-power.com <mailto:jo.goossens at hosted-power.com> > wrote: Hello Atin, ? ? I just read it and very happy you found the issue. We really ho...

...volume's brick info, update the port, and restart glusterd on each node. Luckily I only have four servers! Hoping I don't have to do this every time I reboot! Regards, On Sat, Dec 2, 2017 at 5:23 PM Atin Mukherjee <amukherj at redhat.com> wrote: > On Sat, 2 Dec 2017 at 19:29, Jo Goossens <jo.goossens at hosted-power.com> > wrote: > >> Hello Atin, >> >> >> >> >> >> Could you confirm this should have been fixed in 3.10.8? If so we'll test >> it for sure! >> > > Fix should be part of 3.10.8 which is awaiting r...

...t; node. Luckily I only have four servers! Hoping I don't have to do this >> every time I reboot! >> >> Regards, >> >> On Sat, Dec 2, 2017 at 5:23 PM Atin Mukherjee <amukherj at redhat.com> >> wrote: >> >>> On Sat, 2 Dec 2017 at 19:29, Jo Goossens <jo.goossens at hosted-power.com> >>> wrote: >>> >>>> Hello Atin, >>>> >>>> >>>> >>>> >>>> >>>> Could you confirm this should have been fixed in 3.10.8? If so we'll >>>> test...

On Sat, 2 Dec 2017 at 19:29, Jo Goossens <jo.goossens at hosted-power.com> wrote: > Hello Atin, > > > > > > Could you confirm this should have been fixed in 3.10.8? If so we'll test > it for sure! > Fix should be part of 3.10.8 which is awaiting release announcement. > > Regards > > Jo...

3.10 doesn't have this regression, so you're safe. On Tue, Jan 23, 2018 at 1:28 PM, Jo Goossens <jo.goossens at hosted-power.com> wrote: > Hello, > > > > > > Will we also suffer from this regression in any of the (previously) fixed > 3.10 releases? We kept 3.10 and hope to stay stable :/ > > > > Regards > > Jo > > > > > > ----...

...r servers! Hoping I don't have to do this >>> every time I reboot! >>> >>> Regards, >>> >>> On Sat, Dec 2, 2017 at 5:23 PM Atin Mukherjee <amukherj at redhat.com> >>> wrote: >>> >>>> On Sat, 2 Dec 2017 at 19:29, Jo Goossens <jo.goossens at hosted-power.com> >>>> wrote: >>>> >>>>> Hello Atin, >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Could you confirm this should have been fixed in 3.10.8? If...

...port, and restart glusterd on each > node. Luckily I only have four servers! Hoping I don't have to do this > every time I reboot! > > Regards, > > On Sat, Dec 2, 2017 at 5:23 PM Atin Mukherjee <amukherj at redhat.com> wrote: > >> On Sat, 2 Dec 2017 at 19:29, Jo Goossens <jo.goossens at hosted-power.com> >> wrote: >> >>> Hello Atin, >>> >>> >>> >>> >>> >>> Could you confirm this should have been fixed in 3.10.8? If so we'll >>> test it for sure! >>> >> >&...

We (finally) figured out the root cause, Jo! Patch https://review.gluster.org/#/c/18579 posted upstream for review. On Thu, Sep 21, 2017 at 2:08 PM, Jo Goossens <jo.goossens at hosted-power.com> wrote: > Hi, > > > > > > We use glusterfs 3.10.5 on Debian 9. > > > > When we stop or restart the service, e.g.: service glusterfs-server restart > > > > We see that the wrong port get's advertised afterwards....

..." else echo "!!! NOT OK For ${Brick}" fi done done Met vriendelijke groet, Mike Hulsman Proxy Managed Services B.V. | www.proxy.nl | Enterprise IT-Infra, Open Source and Cloud Technology Delftweg 128 3043 NB Rotterdam The Netherlands | +31 10 307 0965 From: "Jo Goossens" <jo.goossens at hosted-power.com> To: "Atin Mukherjee" <amukherj at redhat.com> Cc: gluster-users at gluster.org Sent: Friday, October 27, 2017 11:06:35 PM Subject: Re: [Gluster-users] BUG: After stop and start wrong port is advertised BQ_BEGIN RE: [Gluster-user...

...a, Open > Source and Cloud Technology > Delftweg 128 3043 NB Rotterdam The Netherlands > <https://maps.google.com/?q=Delftweg+128+3043+NB+Rotterdam+The+Netherlands&entry=gmail&source=g> > | +31 10 307 0965 > > ------------------------------ > > *From: *"Jo Goossens" <jo.goossens at hosted-power.com> > *To: *"Atin Mukherjee" <amukherj at redhat.com> > *Cc: *gluster-users at gluster.org > *Sent: *Friday, October 27, 2017 11:06:35 PM > *Subject: *Re: [Gluster-users] BUG: After stop and start wrong port is > advertised &g...

...y you found the issue. We really hope this will be fixed in the next 3.10.7 version! ? ? PS: Wow nice all that c code and those "goto out" statements (not always considered clean but the best way often I think). Can remember the days I wrote kernel drivers myself in c :) ? ? Regards Jo Goossens ? ? ? -----Original message----- From:Atin Mukherjee <amukherj at redhat.com> Sent:Fri 27-10-2017 21:01 Subject:Re: [Gluster-users] BUG: After stop and start wrong port is advertised To:Jo Goossens <jo.goossens at hosted-power.com>; CC:gluster-users at gluster.org; We (finally) fi...

...'re doing it wrong". https://joejulian.name/blog/optimizing-web-performance-with-glusterfs/ That said, you might also look at these mount options: attribute-timeout, entry-timeout, negative-timeout (set to some large amount of time), and fopen-keep-cache. On 07/11/2017 07:48 AM, Jo Goossens wrote: Hello, ? ? Here is the volume info as requested by soumya: ? #gluster volume info www ? Volume Name: www Type: Replicate Volume ID: 5d64ee36-828a-41fa-adbf-75718b954aff Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Brick...

...s to solve so many problems, is there anyone knowledgeable why this is the case?? ? This would better be default I suppose ...? ? I'm still wondering if there is a big underlying issue in gluster causing the difference to be so gigantic. Regards Jo ? ? -----Original message----- From:Jo Goossens <jo.goossens at hosted-power.com> Sent:Tue 11-07-2017 18:48 Subject:RE: [Gluster-users] Gluster native mount is really slow compared to nfs CC:gluster-users at gluster.org; To:Vijay Bellur <vbellur at redhat.com>; PS: I just tested between these 2: ? mount -t glusterfs -o negative...

...erence is made by :?negative-timeout=600 , when removing it, it's much much slower again. ? ? Regards Jo ? -----Original message----- From:Vijay Bellur <vbellur at redhat.com> Sent:Tue 11-07-2017 18:16 Subject:Re: [Gluster-users] Gluster native mount is really slow compared to nfs To:Jo Goossens <jo.goossens at hosted-power.com>; CC:gluster-users at gluster.org; Joe Julian <joe at julianfamily.org>; On Tue, Jul 11, 2017 at 11:39 AM, Jo Goossens <jo.goossens at hosted-power.com <mailto:jo.goossens at hosted-power.com> > wrote: Hello Joe, ? ? I just did a mo...

On 07/11/2017 08:14 AM, Jo Goossens wrote: > RE: [Gluster-users] Gluster native mount is really slow compared to nfs > > Hello Joe, > > I really appreciate your feedback, but I already tried the opcache > stuff (to not valildate at all). It improves of course then, but not > completely somehow. Still quite slow...

...k into it on monday fortunately :) Regards Jo ? ? ? -----Original message----- From:Darrell Budic <budic at onholyground.com> Sent:Fri 22-09-2017 17:24 Subject:Re: [Gluster-users] BUG: After stop and start wrong port is advertised To:Atin Mukherjee <amukherj at redhat.com>; CC:Jo Goossens <jo.goossens at hosted-power.com>; gluster-users at gluster.org; I encountered this once in the past, an additional symptom was peers were in disconnected state on the peers that were NOT using the wrong ports. Disconnected peers is how it detected it in the first place. It happened to me a...

...statedump and the file will be available in /var/run/gluster > 2. glusterd, brick logfile for 192.168.140.43:/gluster/public from 192.168.140.43 > 3. cmd_history logfile from all the nodes. > 4. Content of /var/lib/glusterd/vols/public/ > > > On Thu, Sep 21, 2017 at 2:08 PM, Jo Goossens <jo.goossens at hosted-power.com> wrote: > Hi, > > > > We use glusterfs 3.10.5 on Debian 9. > > > When we stop or restart the service, e.g.: service glusterfs-server restart > > > We see that the wrong port get's advertised afterwards. For examp...

...testing over here , because this is ridiculous. That woud mean defaults or no good at all... ? Regards Jo ? -----Original message----- From:Joe Julian <joe at julianfamily.org> Sent:Tue 11-07-2017 17:16 Subject:Re: [Gluster-users] Gluster native mount is really slow compared to nfs To:Jo Goossens <jo.goossens at hosted-power.com>; gluster-users at gluster.org; On 07/11/2017 08:14 AM, Jo Goossens wrote: Hello Joe, ? ? I really appreciate your feedback, but I already tried the opcache stuff (to not valildate at all). It improves of course then, but not completely somehow...