search for: atin

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 ? ? -----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 w...

...> 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 > > > > > > -----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-us...

Hello Atin, I've gotten around to this and was able to get upgrade done using 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't working well. On 3.11 though I notice that gluster/nfs is really made optional and nfs-ganesha is being recommended. We have plans to switch to nfs-ganesha on new...

On Fri, 18 Aug 2017 at 13:45, Raghavendra Talur <rtalur at redhat.com> wrote: > On Fri, Aug 18, 2017 at 1:38 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: > > > > > > On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> > > wrote: > >> > >> You're hitting a race here. By the time glusterd tries to resolve the > >> add...

...led "wingu3"). I hope that's what you need. [0] https://github.com/gluster/glusterfs/blob/release-3.12/doc/release-notes/3.12.3.md [1] https://bugzilla.redhat.com/show_bug.cgi?id=1507747 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1507748 Thanks, On Mon, Jan 22, 2018 at 6:34 AM Atin Mukherjee <amukherj at redhat.com> wrote: > The patch was definitely there in 3.12.3. Do you have the glusterd and > brick logs handy with you when this happened? > > On Sun, Jan 21, 2018 at 10:21 PM, Alan Orth <alan.orth at gmail.com> wrote: > >> For what it's...

On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: > Hello Atin, > > I've gotten around to this and was able to get upgrade done using 3.7.0 > before moving to 3.11. For some reason 3.7.9 wasn't working well. > > On 3.11 though I notice that gluster/nfs is really made optional and > nfs-ganesha is being recommended. We have plans to...

18.08.2017 12:21, Atin Mukherjee ?????: > > On Fri, 18 Aug 2017 at 13:45, Raghavendra Talur <rtalur at redhat.com > <mailto:rtalur at redhat.com>> wrote: > > On Fri, Aug 18, 2017 at 1:38 PM, Atin Mukherjee > <amukherj at redhat.com <mailto:amukherj at redhat.com>> wrote:...

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://review.gluster.org/19146 committed in release-3.12 by \"Atin Mukherjee\" <amukherj at redhat.com> with a commit message- glusterd: connect to an existing brick process when qourum status is NOT_APPLICABLE_QUORUM First of all, this patch reverts commit 635c1c3 as the same is causing a regression with bricks not coming up on time when a node is reb...

...4? I had to use Mike Hulsman's script to check the daemon port against the port in the 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...

Sorry for big attachment in previous mail...last 1000 lines of those logs attached now. On Mon, May 29, 2017 at 4:44 PM, Pawan Alwandi <pawan at platform.sh> wrote: > > > On Thu, May 25, 2017 at 9:54 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: > >> >> On Thu, 25 May 2017 at 19:11, Pawan Alwandi <pawan at platform.sh> wrote: >> >>> Hello Atin, >>> >>> Yes, glusterd on other instances are up and running. Below is the >>> req...

...s script to check the daemon port against the port in > the 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 shoul...

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 > > > > > > > -----Original message----- &g...

Hello Atin, ? ? Could 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 advertise...

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 today. You?ll get this fix in 3.10.8. > > > > PS:...

On Fri, Aug 18, 2017 at 1:38 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > > > On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: >> >> You're hitting a race here. By the time glusterd tries to resolve the >> address of one of the remote bricks of a pa...

On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > You're hitting a race here. By the time glusterd tries to resolve the > address of one of the remote bricks of a particular volume, the n/w > interface is not up by that time. We have fixed this issue in mainline and > 3.12 branch t...

On 07/03/2017 04:34 AM, Atin Mukherjee wrote: > > On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: > > Hello Atin, > > I've gotten around to this and was able to get upgrade done using > 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't working...

...r Tumballi <atumball at redhat.com> > wrote: > > > > > This is already part of 3.11.0 release? > > > > > > On Wed, May 31, 2017 at 3:47 PM, ABHISHEK PALIWAL < > abhishpaliwal at gmail.com > > > > wrote: > > > > > >> Hi Atin, > > >> > > >> Could you please let us know any time plan for deliver of this patch. > > >> > > >> Regards, > > >> Abhishek > > >> > > >> On Tue, May 9, 2017 at 6:37 PM, ABHISHEK PALIWAL < > abhishpaliwal at g...

...10.6 release, and it is not worse than previous versions, I'll mark the packages stable so that they get sync'd to the CentOS mirrors the days afterwards. Thanks, Niels > > > Thanks in advance > > > Ismael > > > ________________________________ > De : Atin Mukherjee <amukherj at redhat.com> > Envoy? : dimanche 17 septembre 2017 14:56 > ? : ismael mondiu > Cc : Niels de Vos; gluster-users at gluster.org; Gaurav Yadav > Objet : Re: [Gluster-users] Glusterd not working with systemd in redhat 7 > > The backport just got merged fe...

Hello, I'd like to test if 3.10.6 version fixes the problem . I'm wondering which is the correct way to upgrade from 3.10.5 to 3.10.6. It's hard to find upgrade guides for a minor release. Can you help me please ? Thanks in advance Ismael ________________________________ De : Atin Mukherjee <amukherj at redhat.com> Envoy? : dimanche 17 septembre 2017 14:56 ? : ismael mondiu Cc : Niels de Vos; gluster-users at gluster.org; Gaurav Yadav Objet : Re: [Gluster-users] Glusterd not working with systemd in redhat 7 The backport just got merged few minutes back and this fix sh...