Release 4.1.10: Expected tagging on July 15th

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Release 4.1.10: Expected tagging on July 15th

Hari Gowtham
Hi,

Expected tagging date for release-4.1.10 is on July, 15th 2019.

NOTE: This is the last release for 4 series.

Branch 4 will be EOLed after this. So if there are any critical patches
please ensure they are backported and also are passing
regressions and are appropriately reviewed for easy merging and tagging
on the date.

--
Regards,
Hari Gowtham.
_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: Release 4.1.10: Expected tagging on July 15th

Pasi Kärkkäinen
On Tue, Jul 09, 2019 at 02:32:46PM +0530, Hari Gowtham wrote:

> Hi,
>
> Expected tagging date for release-4.1.10 is on July, 15th 2019.
>
> NOTE: This is the last release for 4 series.
>
> Branch 4 will be EOLed after this. So if there are any critical patches
> please ensure they are backported and also are passing
> regressions and are appropriately reviewed for easy merging and tagging
> on the date.
>

Glusterfs 4.1.9 did close this issue:

"gfapi: do not block epoll thread for upcall notifications":
https://bugzilla.redhat.com/show_bug.cgi?id=1694563


But more patches are needed to properly fix the issue, so it'd really nice to have these patches backported to 4.1.10 aswell:

"gfapi: fix incorrect initialization of upcall syncop arguments":
https://bugzilla.redhat.com/show_bug.cgi?id=1718316

"Upcall: Avoid sending upcalls for invalid Inode":
https://bugzilla.redhat.com/show_bug.cgi?id=1718338


This gfapi/upcall issue gets easily triggered with nfs-ganesha, and causes "complete IO hang", as can be seem here:

"Complete IO hang on CentOS 7.5":
https://github.com/nfs-ganesha/nfs-ganesha/issues/335


Thanks,

-- Pasi

 
> --
> Regards,
> Hari Gowtham.
 
_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: Release 4.1.10: Expected tagging on July 15th

Soumya Koduri


On 7/11/19 5:34 PM, Pasi Kärkkäinen wrote:

> On Tue, Jul 09, 2019 at 02:32:46PM +0530, Hari Gowtham wrote:
>> Hi,
>>
>> Expected tagging date for release-4.1.10 is on July, 15th 2019.
>>
>> NOTE: This is the last release for 4 series.
>>
>> Branch 4 will be EOLed after this. So if there are any critical patches
>> please ensure they are backported and also are passing
>> regressions and are appropriately reviewed for easy merging and tagging
>> on the date.
>>
>
> Glusterfs 4.1.9 did close this issue:
>
> "gfapi: do not block epoll thread for upcall notifications":
> https://bugzilla.redhat.com/show_bug.cgi?id=1694563
>
>
> But more patches are needed to properly fix the issue, so it'd really nice to have these patches backported to 4.1.10 aswell:
>
> "gfapi: fix incorrect initialization of upcall syncop arguments":
> https://bugzilla.redhat.com/show_bug.cgi?id=1718316
>
> "Upcall: Avoid sending upcalls for invalid Inode":
> https://bugzilla.redhat.com/show_bug.cgi?id=1718338
>
>
> This gfapi/upcall issue gets easily triggered with nfs-ganesha, and causes "complete IO hang", as can be seem here:
>
> "Complete IO hang on CentOS 7.5":
> https://github.com/nfs-ganesha/nfs-ganesha/issues/335

Thanks Pasi.

@Hari,

The smoke tests have passed for these patches now. Kindly merge them.

Thanks,
Soumya

>
>
> Thanks,
>
> -- Pasi
>
>  
>> --
>> Regards,
>> Hari Gowtham.
>  
> _______________________________________________
>
> Community Meeting Calendar:
>
> APAC Schedule -
> Every 2nd and 4th Tuesday at 11:30 AM IST
> Bridge: https://bluejeans.com/836554017
>
> NA/EMEA Schedule -
> Every 1st and 3rd Tuesday at 01:00 PM EDT
> Bridge: https://bluejeans.com/486278655
>
> Gluster-devel mailing list
> [hidden email]
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>
_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply | Threaded
Open this post in threaded view
|

Re: Release 4.1.10: Expected tagging on July 15th

Hari Gowtham
Thanks Soumya.
Have merged them.

On Tue, Jul 16, 2019 at 8:07 PM Soumya Koduri <[hidden email]> wrote:

>
>
>
> On 7/11/19 5:34 PM, Pasi Kärkkäinen wrote:
> > On Tue, Jul 09, 2019 at 02:32:46PM +0530, Hari Gowtham wrote:
> >> Hi,
> >>
> >> Expected tagging date for release-4.1.10 is on July, 15th 2019.
> >>
> >> NOTE: This is the last release for 4 series.
> >>
> >> Branch 4 will be EOLed after this. So if there are any critical patches
> >> please ensure they are backported and also are passing
> >> regressions and are appropriately reviewed for easy merging and tagging
> >> on the date.
> >>
> >
> > Glusterfs 4.1.9 did close this issue:
> >
> > "gfapi: do not block epoll thread for upcall notifications":
> > https://bugzilla.redhat.com/show_bug.cgi?id=1694563
> >
> >
> > But more patches are needed to properly fix the issue, so it'd really nice to have these patches backported to 4.1.10 aswell:
> >
> > "gfapi: fix incorrect initialization of upcall syncop arguments":
> > https://bugzilla.redhat.com/show_bug.cgi?id=1718316
> >
> > "Upcall: Avoid sending upcalls for invalid Inode":
> > https://bugzilla.redhat.com/show_bug.cgi?id=1718338
> >
> >
> > This gfapi/upcall issue gets easily triggered with nfs-ganesha, and causes "complete IO hang", as can be seem here:
> >
> > "Complete IO hang on CentOS 7.5":
> > https://github.com/nfs-ganesha/nfs-ganesha/issues/335
>
> Thanks Pasi.
>
> @Hari,
>
> The smoke tests have passed for these patches now. Kindly merge them.
>
> Thanks,
> Soumya
>
> >
> >
> > Thanks,
> >
> > -- Pasi
> >
> >
> >> --
> >> Regards,
> >> Hari Gowtham.
> >
> > _______________________________________________
> >
> > Community Meeting Calendar:
> >
> > APAC Schedule -
> > Every 2nd and 4th Tuesday at 11:30 AM IST
> > Bridge: https://bluejeans.com/836554017
> >
> > NA/EMEA Schedule -
> > Every 1st and 3rd Tuesday at 01:00 PM EDT
> > Bridge: https://bluejeans.com/486278655
> >
> > Gluster-devel mailing list
> > [hidden email]
> > https://lists.gluster.org/mailman/listinfo/gluster-devel
> >



--
Regards,
Hari Gowtham.
_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/836554017

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/486278655

Gluster-devel mailing list
[hidden email]
https://lists.gluster.org/mailman/listinfo/gluster-devel