Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

Thanks Akira and Surendra for pointing that out.

Looks I missed after creating the branch..



On Thu, 30 Apr 2020 at 10:16 AM, Akira Ajisaka  wrote:

> Hi Surendra,
>
> Updated the version to 3.3.1-SNAPSHOT in branch-3.3.
>
> Thanks,
> Akira
>
> On Wed, Apr 29, 2020 at 4:22 PM Surendra Singh Lilhore <
> surendralilh...@gmail.com> wrote:
>
>> Hi Brahma,
>>
>> Why the branch-3.3 & branch-3.3.0 pom version is same ?.
>>
>> In branch-3.3 pom version should be 3.3.1.
>>
>> Please correct me if I am wrong.
>>
>> -Surendra
>>
>>
>> On Sat, 25 Apr, 2020, 9:33 am Mingliang Liu,  wrote:
>>
>> > Brahma,
>> >
>> > What about https://issues.apache.org/jira/browse/HADOOP-17007?
>> >
>> > Thanks,
>> >
>> > On Fri, Apr 24, 2020 at 11:07 AM Brahma Reddy Battula <
>> bra...@apache.org>
>> > wrote:
>> >
>> > > Ok. Done. Branch created.
>> > >
>> > > Following blockers are pending, will closely track this.
>> > >
>> > > https://issues.apache.org/jira/browse/HDFS-15287 ( Open: Under
>> > discussion
>> > > )
>> > > https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available)
>> > > https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available)
>> > > https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available)
>> > >
>> > >
>> > > On Fri, Apr 24, 2020 at 7:42 PM Wei-Chiu Chuang
>> > >  wrote:
>> > >
>> > > > +1 we should have the branch ASAP.
>> > > >
>> > > > On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka > >
>> > > > wrote:
>> > > >
>> > > > > > Since blockers are not closed, I didn't cut the branch because
>> > > > > multiple branches might confuse or sombody might miss to commit.
>> > > > >
>> > > > > The current situation is already confusing. The 3.3.1 version
>> already
>> > > > > exists in JIRA, so some committers wrongly commit non-critical
>> issues
>> > > to
>> > > > > branch-3.3 and set the fix version to 3.3.1.
>> > > > > I think now we should cut branch-3.3.0 and freeze source code
>> except
>> > > the
>> > > > > blockers.
>> > > > >
>> > > > > -Akira
>> > > > >
>> > > > > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula <
>> > > bra...@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > >> Sure, I will do that.
>> > > > >>
>> > > > >> Since blockers are not closed, I didn't cut the branch because
>> > > > >> multiple branches might confuse or sombody might miss to
>> > commit.Shall
>> > > I
>> > > > >> wait till this weekend to create..?
>> > > > >>
>> > > > >> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka <
>> aajis...@apache.org
>> > >
>> > > > >> wrote:
>> > > > >>
>> > > > >>> Hi Brahma,
>> > > > >>>
>> > > > >>> Thank you for preparing the release.
>> > > > >>> Could you cut branch-3.3.0? I would like to backport some fixes
>> for
>> > > > >>> 3.3.1 and not for 3.3.0.
>> > > > >>>
>> > > > >>> Thanks and regards,
>> > > > >>> Akira
>> > > > >>>
>> > > > >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula <
>> > > > bra...@apache.org>
>> > > > >>> wrote:
>> > > > >>>
>> > > >  Hi All,
>> > > > 
>> > > >  we are down to two blockers issues now (YARN-10194 and
>> YARN-9848)
>> > > > which
>> > > >  are in patch available state.Hopefully we can out the RC soon.
>> > > > 
>> > > >  thanks to @Prabhu Joseph 
>> > > > ,@masakate,@akira
>> > > >  and @Wei-Chiu Chuang   and others for
>> > helping
>> > > >  resloving the blockers.
>> > > > 
>> > > > 
>> > > > 
>> > > >  On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
>> > > >  bra...@apache.org> wrote:
>> > > > 
>> > > > >
>> > > > > @Prabhu Joseph 
>> > > > > >>> Have committed the YARN blocker YARN-10219 to trunk and
>> > > > > cherry-picked to branch-3.3. Right now, there are two blocker
>> > > Jiras -
>> > > > > YARN-10233 and HADOOP-16982
>> > > > > which i will help to review and commit. Thanks.
>> > > > >
>> > > > > Looks you committed YARN-10219. Noted YARN-10233 and
>> HADOOP-16982
>> > > as
>> > > > a
>> > > > > blockers. (without YARN-10233 we have given so many
>> releases,it's
>> > > > not newly
>> > > > > introduced.).. Thanks
>> > > > >
>> > > > > @Vinod Kumar Vavilapalli  ,@adam
>> Antal,
>> > > > >
>> > > > > I noted YARN-9848 as a blocker as you mentioned above.
>> > > > >
>> > > > > @All,
>> > > > >
>> > > > > Currently following four blockers are pending for 3.3.0 RC.
>> > > > >
>> > > > > HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
>> > > > > vino...@apache.org> wrote:
>> > > > >
>> > > > >> Looks like a really bad bug to me.
>> > > > >>
>> > > > >> +1 for revert and +1 for making that a 3.3.0 blocker. I think
>> > > should
>> > > > >> also revert it in a 3.2 maintenance release too.
>> > > > >>
>> > > > >> Thanks
>> > > > >> +Vinod
>> > > > >>
>> > > > >> > On Apr 14, 2020, at 5:03 PM, Adam Antal <
>> > > 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Akira Ajisaka]

Hi Surendra,

Updated the version to 3.3.1-SNAPSHOT in branch-3.3.

Thanks,
Akira

On Wed, Apr 29, 2020 at 4:22 PM Surendra Singh Lilhore <
surendralilh...@gmail.com> wrote:

> Hi Brahma,
>
> Why the branch-3.3 & branch-3.3.0 pom version is same ?.
>
> In branch-3.3 pom version should be 3.3.1.
>
> Please correct me if I am wrong.
>
> -Surendra
>
>
> On Sat, 25 Apr, 2020, 9:33 am Mingliang Liu,  wrote:
>
> > Brahma,
> >
> > What about https://issues.apache.org/jira/browse/HADOOP-17007?
> >
> > Thanks,
> >
> > On Fri, Apr 24, 2020 at 11:07 AM Brahma Reddy Battula  >
> > wrote:
> >
> > > Ok. Done. Branch created.
> > >
> > > Following blockers are pending, will closely track this.
> > >
> > > https://issues.apache.org/jira/browse/HDFS-15287 ( Open: Under
> > discussion
> > > )
> > > https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available)
> > > https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available)
> > > https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available)
> > >
> > >
> > > On Fri, Apr 24, 2020 at 7:42 PM Wei-Chiu Chuang
> > >  wrote:
> > >
> > > > +1 we should have the branch ASAP.
> > > >
> > > > On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka 
> > > > wrote:
> > > >
> > > > > > Since blockers are not closed, I didn't cut the branch because
> > > > > multiple branches might confuse or sombody might miss to commit.
> > > > >
> > > > > The current situation is already confusing. The 3.3.1 version
> already
> > > > > exists in JIRA, so some committers wrongly commit non-critical
> issues
> > > to
> > > > > branch-3.3 and set the fix version to 3.3.1.
> > > > > I think now we should cut branch-3.3.0 and freeze source code
> except
> > > the
> > > > > blockers.
> > > > >
> > > > > -Akira
> > > > >
> > > > > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula <
> > > bra...@apache.org>
> > > > > wrote:
> > > > >
> > > > >> Sure, I will do that.
> > > > >>
> > > > >> Since blockers are not closed, I didn't cut the branch because
> > > > >> multiple branches might confuse or sombody might miss to
> > commit.Shall
> > > I
> > > > >> wait till this weekend to create..?
> > > > >>
> > > > >> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka <
> aajis...@apache.org
> > >
> > > > >> wrote:
> > > > >>
> > > > >>> Hi Brahma,
> > > > >>>
> > > > >>> Thank you for preparing the release.
> > > > >>> Could you cut branch-3.3.0? I would like to backport some fixes
> for
> > > > >>> 3.3.1 and not for 3.3.0.
> > > > >>>
> > > > >>> Thanks and regards,
> > > > >>> Akira
> > > > >>>
> > > > >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula <
> > > > bra...@apache.org>
> > > > >>> wrote:
> > > > >>>
> > > >  Hi All,
> > > > 
> > > >  we are down to two blockers issues now (YARN-10194 and
> YARN-9848)
> > > > which
> > > >  are in patch available state.Hopefully we can out the RC soon.
> > > > 
> > > >  thanks to @Prabhu Joseph 
> > > > ,@masakate,@akira
> > > >  and @Wei-Chiu Chuang   and others for
> > helping
> > > >  resloving the blockers.
> > > > 
> > > > 
> > > > 
> > > >  On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
> > > >  bra...@apache.org> wrote:
> > > > 
> > > > >
> > > > > @Prabhu Joseph 
> > > > > >>> Have committed the YARN blocker YARN-10219 to trunk and
> > > > > cherry-picked to branch-3.3. Right now, there are two blocker
> > > Jiras -
> > > > > YARN-10233 and HADOOP-16982
> > > > > which i will help to review and commit. Thanks.
> > > > >
> > > > > Looks you committed YARN-10219. Noted YARN-10233 and
> HADOOP-16982
> > > as
> > > > a
> > > > > blockers. (without YARN-10233 we have given so many
> releases,it's
> > > > not newly
> > > > > introduced.).. Thanks
> > > > >
> > > > > @Vinod Kumar Vavilapalli  ,@adam
> Antal,
> > > > >
> > > > > I noted YARN-9848 as a blocker as you mentioned above.
> > > > >
> > > > > @All,
> > > > >
> > > > > Currently following four blockers are pending for 3.3.0 RC.
> > > > >
> > > > > HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> > > > > vino...@apache.org> wrote:
> > > > >
> > > > >> Looks like a really bad bug to me.
> > > > >>
> > > > >> +1 for revert and +1 for making that a 3.3.0 blocker. I think
> > > should
> > > > >> also revert it in a 3.2 maintenance release too.
> > > > >>
> > > > >> Thanks
> > > > >> +Vinod
> > > > >>
> > > > >> > On Apr 14, 2020, at 5:03 PM, Adam Antal <
> > > adam.an...@cloudera.com
> > > > .INVALID>
> > > > >> wrote:
> > > > >> >
> > > > >> > Hi everyone,
> > > > >> >
> > > > >> > Sorry for coming a bit late with this, but there's also one
> > jira
> > > > >> that can
> > > > >> > have potential impact on clusters and we should talk about
> it.
> > > > >> >
> > > > 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Surendra Singh Lilhore]

Hi Brahma,

Why the branch-3.3 & branch-3.3.0 pom version is same ?.

In branch-3.3 pom version should be 3.3.1.

Please correct me if I am wrong.

-Surendra


On Sat, 25 Apr, 2020, 9:33 am Mingliang Liu,  wrote:

> Brahma,
>
> What about https://issues.apache.org/jira/browse/HADOOP-17007?
>
> Thanks,
>
> On Fri, Apr 24, 2020 at 11:07 AM Brahma Reddy Battula 
> wrote:
>
> > Ok. Done. Branch created.
> >
> > Following blockers are pending, will closely track this.
> >
> > https://issues.apache.org/jira/browse/HDFS-15287 ( Open: Under
> discussion
> > )
> > https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available)
> > https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available)
> > https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available)
> >
> >
> > On Fri, Apr 24, 2020 at 7:42 PM Wei-Chiu Chuang
> >  wrote:
> >
> > > +1 we should have the branch ASAP.
> > >
> > > On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka 
> > > wrote:
> > >
> > > > > Since blockers are not closed, I didn't cut the branch because
> > > > multiple branches might confuse or sombody might miss to commit.
> > > >
> > > > The current situation is already confusing. The 3.3.1 version already
> > > > exists in JIRA, so some committers wrongly commit non-critical issues
> > to
> > > > branch-3.3 and set the fix version to 3.3.1.
> > > > I think now we should cut branch-3.3.0 and freeze source code except
> > the
> > > > blockers.
> > > >
> > > > -Akira
> > > >
> > > > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula <
> > bra...@apache.org>
> > > > wrote:
> > > >
> > > >> Sure, I will do that.
> > > >>
> > > >> Since blockers are not closed, I didn't cut the branch because
> > > >> multiple branches might confuse or sombody might miss to
> commit.Shall
> > I
> > > >> wait till this weekend to create..?
> > > >>
> > > >> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka  >
> > > >> wrote:
> > > >>
> > > >>> Hi Brahma,
> > > >>>
> > > >>> Thank you for preparing the release.
> > > >>> Could you cut branch-3.3.0? I would like to backport some fixes for
> > > >>> 3.3.1 and not for 3.3.0.
> > > >>>
> > > >>> Thanks and regards,
> > > >>> Akira
> > > >>>
> > > >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula <
> > > bra...@apache.org>
> > > >>> wrote:
> > > >>>
> > >  Hi All,
> > > 
> > >  we are down to two blockers issues now (YARN-10194 and YARN-9848)
> > > which
> > >  are in patch available state.Hopefully we can out the RC soon.
> > > 
> > >  thanks to @Prabhu Joseph 
> > > ,@masakate,@akira
> > >  and @Wei-Chiu Chuang   and others for
> helping
> > >  resloving the blockers.
> > > 
> > > 
> > > 
> > >  On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
> > >  bra...@apache.org> wrote:
> > > 
> > > >
> > > > @Prabhu Joseph 
> > > > >>> Have committed the YARN blocker YARN-10219 to trunk and
> > > > cherry-picked to branch-3.3. Right now, there are two blocker
> > Jiras -
> > > > YARN-10233 and HADOOP-16982
> > > > which i will help to review and commit. Thanks.
> > > >
> > > > Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982
> > as
> > > a
> > > > blockers. (without YARN-10233 we have given so many releases,it's
> > > not newly
> > > > introduced.).. Thanks
> > > >
> > > > @Vinod Kumar Vavilapalli  ,@adam Antal,
> > > >
> > > > I noted YARN-9848 as a blocker as you mentioned above.
> > > >
> > > > @All,
> > > >
> > > > Currently following four blockers are pending for 3.3.0 RC.
> > > >
> > > > HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
> > > >
> > > >
> > > >
> > > > On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> > > > vino...@apache.org> wrote:
> > > >
> > > >> Looks like a really bad bug to me.
> > > >>
> > > >> +1 for revert and +1 for making that a 3.3.0 blocker. I think
> > should
> > > >> also revert it in a 3.2 maintenance release too.
> > > >>
> > > >> Thanks
> > > >> +Vinod
> > > >>
> > > >> > On Apr 14, 2020, at 5:03 PM, Adam Antal <
> > adam.an...@cloudera.com
> > > .INVALID>
> > > >> wrote:
> > > >> >
> > > >> > Hi everyone,
> > > >> >
> > > >> > Sorry for coming a bit late with this, but there's also one
> jira
> > > >> that can
> > > >> > have potential impact on clusters and we should talk about it.
> > > >> >
> > > >> > Steven Rand found this problem earlier and commented to
> > > >> > https://issues.apache.org/jira/browse/YARN-4946.
> > > >> > The bug has impact on the RM state store: the RM does not
> delete
> > > >> apps - see
> > > >> > more details in his comment here:
> > > >> >
> > > >>
> > >
> >
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
> > > >> > .
> > > >> > (FYI 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Mingliang Liu]

Brahma,

What about https://issues.apache.org/jira/browse/HADOOP-17007?

Thanks,

On Fri, Apr 24, 2020 at 11:07 AM Brahma Reddy Battula 
wrote:

> Ok. Done. Branch created.
>
> Following blockers are pending, will closely track this.
>
> https://issues.apache.org/jira/browse/HDFS-15287 ( Open: Under discussion
> )
> https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available)
> https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available)
> https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available)
>
>
> On Fri, Apr 24, 2020 at 7:42 PM Wei-Chiu Chuang
>  wrote:
>
> > +1 we should have the branch ASAP.
> >
> > On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka 
> > wrote:
> >
> > > > Since blockers are not closed, I didn't cut the branch because
> > > multiple branches might confuse or sombody might miss to commit.
> > >
> > > The current situation is already confusing. The 3.3.1 version already
> > > exists in JIRA, so some committers wrongly commit non-critical issues
> to
> > > branch-3.3 and set the fix version to 3.3.1.
> > > I think now we should cut branch-3.3.0 and freeze source code except
> the
> > > blockers.
> > >
> > > -Akira
> > >
> > > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula <
> bra...@apache.org>
> > > wrote:
> > >
> > >> Sure, I will do that.
> > >>
> > >> Since blockers are not closed, I didn't cut the branch because
> > >> multiple branches might confuse or sombody might miss to commit.Shall
> I
> > >> wait till this weekend to create..?
> > >>
> > >> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
> > >> wrote:
> > >>
> > >>> Hi Brahma,
> > >>>
> > >>> Thank you for preparing the release.
> > >>> Could you cut branch-3.3.0? I would like to backport some fixes for
> > >>> 3.3.1 and not for 3.3.0.
> > >>>
> > >>> Thanks and regards,
> > >>> Akira
> > >>>
> > >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula <
> > bra...@apache.org>
> > >>> wrote:
> > >>>
> >  Hi All,
> > 
> >  we are down to two blockers issues now (YARN-10194 and YARN-9848)
> > which
> >  are in patch available state.Hopefully we can out the RC soon.
> > 
> >  thanks to @Prabhu Joseph 
> > ,@masakate,@akira
> >  and @Wei-Chiu Chuang   and others for helping
> >  resloving the blockers.
> > 
> > 
> > 
> >  On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
> >  bra...@apache.org> wrote:
> > 
> > >
> > > @Prabhu Joseph 
> > > >>> Have committed the YARN blocker YARN-10219 to trunk and
> > > cherry-picked to branch-3.3. Right now, there are two blocker
> Jiras -
> > > YARN-10233 and HADOOP-16982
> > > which i will help to review and commit. Thanks.
> > >
> > > Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982
> as
> > a
> > > blockers. (without YARN-10233 we have given so many releases,it's
> > not newly
> > > introduced.).. Thanks
> > >
> > > @Vinod Kumar Vavilapalli  ,@adam Antal,
> > >
> > > I noted YARN-9848 as a blocker as you mentioned above.
> > >
> > > @All,
> > >
> > > Currently following four blockers are pending for 3.3.0 RC.
> > >
> > > HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
> > >
> > >
> > >
> > > On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> > > vino...@apache.org> wrote:
> > >
> > >> Looks like a really bad bug to me.
> > >>
> > >> +1 for revert and +1 for making that a 3.3.0 blocker. I think
> should
> > >> also revert it in a 3.2 maintenance release too.
> > >>
> > >> Thanks
> > >> +Vinod
> > >>
> > >> > On Apr 14, 2020, at 5:03 PM, Adam Antal <
> adam.an...@cloudera.com
> > .INVALID>
> > >> wrote:
> > >> >
> > >> > Hi everyone,
> > >> >
> > >> > Sorry for coming a bit late with this, but there's also one jira
> > >> that can
> > >> > have potential impact on clusters and we should talk about it.
> > >> >
> > >> > Steven Rand found this problem earlier and commented to
> > >> > https://issues.apache.org/jira/browse/YARN-4946.
> > >> > The bug has impact on the RM state store: the RM does not delete
> > >> apps - see
> > >> > more details in his comment here:
> > >> >
> > >>
> >
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
> > >> > .
> > >> > (FYI He also created
> > >> https://issues.apache.org/jira/browse/YARN-9848 with
> > >> > the revert task).
> > >> >
> > >> > It might not be an actual blocker, but since there wasn't any
> > >> consensus
> > >> > about a follow up action, I thought we should decide how to
> > proceed
> > >> before
> > >> > release 3.3.0.
> > >> >
> > >> > Regards,
> > >> > Adam
> > >> >
> > >> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
> > >> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

Ok. Done. Branch created.

Following blockers are pending, will closely track this.

https://issues.apache.org/jira/browse/HDFS-15287 ( Open: Under discussion )
https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available)
https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available)
https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available)


On Fri, Apr 24, 2020 at 7:42 PM Wei-Chiu Chuang
 wrote:

> +1 we should have the branch ASAP.
>
> On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka 
> wrote:
>
> > > Since blockers are not closed, I didn't cut the branch because
> > multiple branches might confuse or sombody might miss to commit.
> >
> > The current situation is already confusing. The 3.3.1 version already
> > exists in JIRA, so some committers wrongly commit non-critical issues to
> > branch-3.3 and set the fix version to 3.3.1.
> > I think now we should cut branch-3.3.0 and freeze source code except the
> > blockers.
> >
> > -Akira
> >
> > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula 
> > wrote:
> >
> >> Sure, I will do that.
> >>
> >> Since blockers are not closed, I didn't cut the branch because
> >> multiple branches might confuse or sombody might miss to commit.Shall I
> >> wait till this weekend to create..?
> >>
> >> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
> >> wrote:
> >>
> >>> Hi Brahma,
> >>>
> >>> Thank you for preparing the release.
> >>> Could you cut branch-3.3.0? I would like to backport some fixes for
> >>> 3.3.1 and not for 3.3.0.
> >>>
> >>> Thanks and regards,
> >>> Akira
> >>>
> >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula <
> bra...@apache.org>
> >>> wrote:
> >>>
>  Hi All,
> 
>  we are down to two blockers issues now (YARN-10194 and YARN-9848)
> which
>  are in patch available state.Hopefully we can out the RC soon.
> 
>  thanks to @Prabhu Joseph 
> ,@masakate,@akira
>  and @Wei-Chiu Chuang   and others for helping
>  resloving the blockers.
> 
> 
> 
>  On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
>  bra...@apache.org> wrote:
> 
> >
> > @Prabhu Joseph 
> > >>> Have committed the YARN blocker YARN-10219 to trunk and
> > cherry-picked to branch-3.3. Right now, there are two blocker Jiras -
> > YARN-10233 and HADOOP-16982
> > which i will help to review and commit. Thanks.
> >
> > Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as
> a
> > blockers. (without YARN-10233 we have given so many releases,it's
> not newly
> > introduced.).. Thanks
> >
> > @Vinod Kumar Vavilapalli  ,@adam Antal,
> >
> > I noted YARN-9848 as a blocker as you mentioned above.
> >
> > @All,
> >
> > Currently following four blockers are pending for 3.3.0 RC.
> >
> > HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
> >
> >
> >
> > On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> > vino...@apache.org> wrote:
> >
> >> Looks like a really bad bug to me.
> >>
> >> +1 for revert and +1 for making that a 3.3.0 blocker. I think should
> >> also revert it in a 3.2 maintenance release too.
> >>
> >> Thanks
> >> +Vinod
> >>
> >> > On Apr 14, 2020, at 5:03 PM, Adam Antal  .INVALID>
> >> wrote:
> >> >
> >> > Hi everyone,
> >> >
> >> > Sorry for coming a bit late with this, but there's also one jira
> >> that can
> >> > have potential impact on clusters and we should talk about it.
> >> >
> >> > Steven Rand found this problem earlier and commented to
> >> > https://issues.apache.org/jira/browse/YARN-4946.
> >> > The bug has impact on the RM state store: the RM does not delete
> >> apps - see
> >> > more details in his comment here:
> >> >
> >>
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
> >> > .
> >> > (FYI He also created
> >> https://issues.apache.org/jira/browse/YARN-9848 with
> >> > the revert task).
> >> >
> >> > It might not be an actual blocker, but since there wasn't any
> >> consensus
> >> > about a follow up action, I thought we should decide how to
> proceed
> >> before
> >> > release 3.3.0.
> >> >
> >> > Regards,
> >> > Adam
> >> >
> >> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
> >> prabhujose.ga...@gmail.com>
> >> > wrote:
> >> >
> >> >> Thanks Brahma for the update.
> >> >>
> >> >> Have committed the YARN blocker YARN-10219 to trunk and
> >> cherry-picked to
> >> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233
> and
> >> >> HADOOP-16982
> >> >> which i will help to review and commit. Thanks.
> >> >>
> >> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
> >> >>
> >> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Wei-Chiu Chuang]

+1 we should have the branch ASAP.

On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka  wrote:

> > Since blockers are not closed, I didn't cut the branch because
> multiple branches might confuse or sombody might miss to commit.
>
> The current situation is already confusing. The 3.3.1 version already
> exists in JIRA, so some committers wrongly commit non-critical issues to
> branch-3.3 and set the fix version to 3.3.1.
> I think now we should cut branch-3.3.0 and freeze source code except the
> blockers.
>
> -Akira
>
> On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula 
> wrote:
>
>> Sure, I will do that.
>>
>> Since blockers are not closed, I didn't cut the branch because
>> multiple branches might confuse or sombody might miss to commit.Shall I
>> wait till this weekend to create..?
>>
>> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
>> wrote:
>>
>>> Hi Brahma,
>>>
>>> Thank you for preparing the release.
>>> Could you cut branch-3.3.0? I would like to backport some fixes for
>>> 3.3.1 and not for 3.3.0.
>>>
>>> Thanks and regards,
>>> Akira
>>>
>>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula 
>>> wrote:
>>>
 Hi All,

 we are down to two blockers issues now (YARN-10194 and YARN-9848) which
 are in patch available state.Hopefully we can out the RC soon.

 thanks to @Prabhu Joseph  ,@masakate,@akira
 and @Wei-Chiu Chuang   and others for helping
 resloving the blockers.



 On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
 bra...@apache.org> wrote:

>
> @Prabhu Joseph 
> >>> Have committed the YARN blocker YARN-10219 to trunk and
> cherry-picked to branch-3.3. Right now, there are two blocker Jiras -
> YARN-10233 and HADOOP-16982
> which i will help to review and commit. Thanks.
>
> Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
> blockers. (without YARN-10233 we have given so many releases,it's not 
> newly
> introduced.).. Thanks
>
> @Vinod Kumar Vavilapalli  ,@adam Antal,
>
> I noted YARN-9848 as a blocker as you mentioned above.
>
> @All,
>
> Currently following four blockers are pending for 3.3.0 RC.
>
> HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
>
>
>
> On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> vino...@apache.org> wrote:
>
>> Looks like a really bad bug to me.
>>
>> +1 for revert and +1 for making that a 3.3.0 blocker. I think should
>> also revert it in a 3.2 maintenance release too.
>>
>> Thanks
>> +Vinod
>>
>> > On Apr 14, 2020, at 5:03 PM, Adam Antal 
>> > 
>> wrote:
>> >
>> > Hi everyone,
>> >
>> > Sorry for coming a bit late with this, but there's also one jira
>> that can
>> > have potential impact on clusters and we should talk about it.
>> >
>> > Steven Rand found this problem earlier and commented to
>> > https://issues.apache.org/jira/browse/YARN-4946.
>> > The bug has impact on the RM state store: the RM does not delete
>> apps - see
>> > more details in his comment here:
>> >
>> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
>> > .
>> > (FYI He also created
>> https://issues.apache.org/jira/browse/YARN-9848 with
>> > the revert task).
>> >
>> > It might not be an actual blocker, but since there wasn't any
>> consensus
>> > about a follow up action, I thought we should decide how to proceed
>> before
>> > release 3.3.0.
>> >
>> > Regards,
>> > Adam
>> >
>> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
>> prabhujose.ga...@gmail.com>
>> > wrote:
>> >
>> >> Thanks Brahma for the update.
>> >>
>> >> Have committed the YARN blocker YARN-10219 to trunk and
>> cherry-picked to
>> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
>> >> HADOOP-16982
>> >> which i will help to review and commit. Thanks.
>> >>
>> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
>> >>
>> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in
>> (Blocker,
>> >> Critical) AND resolution = Unresolved AND "Target Version/s" =
>> 3.3.0 ORDER
>> >> BY priority DESC
>> >>
>> >>
>> >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
>> bra...@apache.org>
>> >> wrote:
>> >>
>> >>> *Pending for 3.3.0 Release:*
>> >>>
>> >>> One Blocker(HADOOP-16963) confirmation and following jira's are
>> open as
>> >>> these needs to merged to other branches(I am tracking the same,
>> Ideally
>> >>> this can be closed and can raise seperate jira's to track).
>> >>>
>> >>>
>> >>> 1–4 of 4Refresh results
>> >>> <
>> >>>
>> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Akira Ajisaka]

> Since blockers are not closed, I didn't cut the branch because
multiple branches might confuse or sombody might miss to commit.

The current situation is already confusing. The 3.3.1 version already
exists in JIRA, so some committers wrongly commit non-critical issues to
branch-3.3 and set the fix version to 3.3.1.
I think now we should cut branch-3.3.0 and freeze source code except the
blockers.

-Akira

On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula 
wrote:

> Sure, I will do that.
>
> Since blockers are not closed, I didn't cut the branch because
> multiple branches might confuse or sombody might miss to commit.Shall I
> wait till this weekend to create..?
>
> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
> wrote:
>
>> Hi Brahma,
>>
>> Thank you for preparing the release.
>> Could you cut branch-3.3.0? I would like to backport some fixes for 3.3.1
>> and not for 3.3.0.
>>
>> Thanks and regards,
>> Akira
>>
>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula 
>> wrote:
>>
>>> Hi All,
>>>
>>> we are down to two blockers issues now (YARN-10194 and YARN-9848) which
>>> are in patch available state.Hopefully we can out the RC soon.
>>>
>>> thanks to @Prabhu Joseph  ,@masakate,@akira
>>> and @Wei-Chiu Chuang   and others for helping
>>> resloving the blockers.
>>>
>>>
>>>
>>> On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula 
>>> wrote:
>>>

 @Prabhu Joseph 
 >>> Have committed the YARN blocker YARN-10219 to trunk and
 cherry-picked to branch-3.3. Right now, there are two blocker Jiras -
 YARN-10233 and HADOOP-16982
 which i will help to review and commit. Thanks.

 Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
 blockers. (without YARN-10233 we have given so many releases,it's not newly
 introduced.).. Thanks

 @Vinod Kumar Vavilapalli  ,@adam Antal,

 I noted YARN-9848 as a blocker as you mentioned above.

 @All,

 Currently following four blockers are pending for 3.3.0 RC.

 HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.



 On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
 vino...@apache.org> wrote:

> Looks like a really bad bug to me.
>
> +1 for revert and +1 for making that a 3.3.0 blocker. I think should
> also revert it in a 3.2 maintenance release too.
>
> Thanks
> +Vinod
>
> > On Apr 14, 2020, at 5:03 PM, Adam Antal 
> > 
> wrote:
> >
> > Hi everyone,
> >
> > Sorry for coming a bit late with this, but there's also one jira
> that can
> > have potential impact on clusters and we should talk about it.
> >
> > Steven Rand found this problem earlier and commented to
> > https://issues.apache.org/jira/browse/YARN-4946.
> > The bug has impact on the RM state store: the RM does not delete
> apps - see
> > more details in his comment here:
> >
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
> > .
> > (FYI He also created https://issues.apache.org/jira/browse/YARN-9848
> with
> > the revert task).
> >
> > It might not be an actual blocker, but since there wasn't any
> consensus
> > about a follow up action, I thought we should decide how to proceed
> before
> > release 3.3.0.
> >
> > Regards,
> > Adam
> >
> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
> prabhujose.ga...@gmail.com>
> > wrote:
> >
> >> Thanks Brahma for the update.
> >>
> >> Have committed the YARN blocker YARN-10219 to trunk and
> cherry-picked to
> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
> >> HADOOP-16982
> >> which i will help to review and commit. Thanks.
> >>
> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
> >>
> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
> >> Critical) AND resolution = Unresolved AND "Target Version/s" =
> 3.3.0 ORDER
> >> BY priority DESC
> >>
> >>
> >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
> bra...@apache.org>
> >> wrote:
> >>
> >>> *Pending for 3.3.0 Release:*
> >>>
> >>> One Blocker(HADOOP-16963) confirmation and following jira's are
> open as
> >>> these needs to merged to other branches(I am tracking the same,
> Ideally
> >>> this can be closed and can raise seperate jira's to track).
> >>>
> >>>
> >>> 1–4 of 4Refresh results
> >>> <
> >>>
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> 
> >>> Columns
> >>> Patch InfoKeyTSummaryAssigneeReporterP
> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Sunil Govindan]

Yes, lets wait till weekend as I can see progress in these blockers.

Thanks
Sunil

On Tue, Apr 21, 2020 at 11:35 AM Brahma Reddy Battula 
wrote:

> Sure, I will do that.
>
> Since blockers are not closed, I didn't cut the branch because
> multiple branches might confuse or sombody might miss to commit.Shall I
> wait till this weekend to create..?
>
> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
> wrote:
>
> > Hi Brahma,
> >
> > Thank you for preparing the release.
> > Could you cut branch-3.3.0? I would like to backport some fixes for 3.3.1
> > and not for 3.3.0.
> >
> > Thanks and regards,
> > Akira
> >
> > On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula  >
> > wrote:
> >
> >> Hi All,
> >>
> >> we are down to two blockers issues now (YARN-10194 and YARN-9848) which
> >> are in patch available state.Hopefully we can out the RC soon.
> >>
> >> thanks to @Prabhu Joseph  ,@masakate,@akira
> >> and @Wei-Chiu Chuang   and others for helping
> >> resloving the blockers.
> >>
> >>
> >>
> >> On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
> bra...@apache.org>
> >> wrote:
> >>
> >>>
> >>> @Prabhu Joseph 
> >>> >>> Have committed the YARN blocker YARN-10219 to trunk and
> >>> cherry-picked to branch-3.3. Right now, there are two blocker Jiras -
> >>> YARN-10233 and HADOOP-16982
> >>> which i will help to review and commit. Thanks.
> >>>
> >>> Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
> >>> blockers. (without YARN-10233 we have given so many releases,it's not
> newly
> >>> introduced.).. Thanks
> >>>
> >>> @Vinod Kumar Vavilapalli  ,@adam Antal,
> >>>
> >>> I noted YARN-9848 as a blocker as you mentioned above.
> >>>
> >>> @All,
> >>>
> >>> Currently following four blockers are pending for 3.3.0 RC.
> >>>
> >>> HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
> >>>
> >>>
> >>>
> >>> On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> >>> vino...@apache.org> wrote:
> >>>
>  Looks like a really bad bug to me.
> 
>  +1 for revert and +1 for making that a 3.3.0 blocker. I think should
>  also revert it in a 3.2 maintenance release too.
> 
>  Thanks
>  +Vinod
> 
>  > On Apr 14, 2020, at 5:03 PM, Adam Antal  .INVALID>
>  wrote:
>  >
>  > Hi everyone,
>  >
>  > Sorry for coming a bit late with this, but there's also one jira
> that
>  can
>  > have potential impact on clusters and we should talk about it.
>  >
>  > Steven Rand found this problem earlier and commented to
>  > https://issues.apache.org/jira/browse/YARN-4946.
>  > The bug has impact on the RM state store: the RM does not delete
> apps
>  - see
>  > more details in his comment here:
>  >
> 
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
>  > .
>  > (FYI He also created
> https://issues.apache.org/jira/browse/YARN-9848
>  with
>  > the revert task).
>  >
>  > It might not be an actual blocker, but since there wasn't any
>  consensus
>  > about a follow up action, I thought we should decide how to proceed
>  before
>  > release 3.3.0.
>  >
>  > Regards,
>  > Adam
>  >
>  > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
>  prabhujose.ga...@gmail.com>
>  > wrote:
>  >
>  >> Thanks Brahma for the update.
>  >>
>  >> Have committed the YARN blocker YARN-10219 to trunk and
>  cherry-picked to
>  >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
>  >> HADOOP-16982
>  >> which i will help to review and commit. Thanks.
>  >>
>  >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
>  >>
>  >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in
> (Blocker,
>  >> Critical) AND resolution = Unresolved AND "Target Version/s" =
> 3.3.0
>  ORDER
>  >> BY priority DESC
>  >>
>  >>
>  >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
>  bra...@apache.org>
>  >> wrote:
>  >>
>  >>> *Pending for 3.3.0 Release:*
>  >>>
>  >>> One Blocker(HADOOP-16963) confirmation and following jira's are
>  open as
>  >>> these needs to merged to other branches(I am tracking the same,
>  Ideally
>  >>> this can be closed and can raise seperate jira's to track).
>  >>>
>  >>>
>  >>> 1–4 of 4Refresh results
>  >>> <
>  >>>
> 
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
>  
>  >>> Columns
>  >>> Patch InfoKeyTSummaryAssigneeReporterP
>  StatusResolutionUpdatedDueCreated
>  >>>  HDFS-14353
>  >>>  

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

Sure, I will do that.

Since blockers are not closed, I didn't cut the branch because
multiple branches might confuse or sombody might miss to commit.Shall I
wait till this weekend to create..?

On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka  wrote:

> Hi Brahma,
>
> Thank you for preparing the release.
> Could you cut branch-3.3.0? I would like to backport some fixes for 3.3.1
> and not for 3.3.0.
>
> Thanks and regards,
> Akira
>
> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula 
> wrote:
>
>> Hi All,
>>
>> we are down to two blockers issues now (YARN-10194 and YARN-9848) which
>> are in patch available state.Hopefully we can out the RC soon.
>>
>> thanks to @Prabhu Joseph  ,@masakate,@akira
>> and @Wei-Chiu Chuang   and others for helping
>> resloving the blockers.
>>
>>
>>
>> On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula 
>> wrote:
>>
>>>
>>> @Prabhu Joseph 
>>> >>> Have committed the YARN blocker YARN-10219 to trunk and
>>> cherry-picked to branch-3.3. Right now, there are two blocker Jiras -
>>> YARN-10233 and HADOOP-16982
>>> which i will help to review and commit. Thanks.
>>>
>>> Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
>>> blockers. (without YARN-10233 we have given so many releases,it's not newly
>>> introduced.).. Thanks
>>>
>>> @Vinod Kumar Vavilapalli  ,@adam Antal,
>>>
>>> I noted YARN-9848 as a blocker as you mentioned above.
>>>
>>> @All,
>>>
>>> Currently following four blockers are pending for 3.3.0 RC.
>>>
>>> HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
>>>
>>>
>>>
>>> On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
>>> vino...@apache.org> wrote:
>>>
 Looks like a really bad bug to me.

 +1 for revert and +1 for making that a 3.3.0 blocker. I think should
 also revert it in a 3.2 maintenance release too.

 Thanks
 +Vinod

 > On Apr 14, 2020, at 5:03 PM, Adam Antal 
 wrote:
 >
 > Hi everyone,
 >
 > Sorry for coming a bit late with this, but there's also one jira that
 can
 > have potential impact on clusters and we should talk about it.
 >
 > Steven Rand found this problem earlier and commented to
 > https://issues.apache.org/jira/browse/YARN-4946.
 > The bug has impact on the RM state store: the RM does not delete apps
 - see
 > more details in his comment here:
 >
 https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
 > .
 > (FYI He also created https://issues.apache.org/jira/browse/YARN-9848
 with
 > the revert task).
 >
 > It might not be an actual blocker, but since there wasn't any
 consensus
 > about a follow up action, I thought we should decide how to proceed
 before
 > release 3.3.0.
 >
 > Regards,
 > Adam
 >
 > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
 prabhujose.ga...@gmail.com>
 > wrote:
 >
 >> Thanks Brahma for the update.
 >>
 >> Have committed the YARN blocker YARN-10219 to trunk and
 cherry-picked to
 >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
 >> HADOOP-16982
 >> which i will help to review and commit. Thanks.
 >>
 >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
 >>
 >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
 >> Critical) AND resolution = Unresolved AND "Target Version/s" = 3.3.0
 ORDER
 >> BY priority DESC
 >>
 >>
 >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
 bra...@apache.org>
 >> wrote:
 >>
 >>> *Pending for 3.3.0 Release:*
 >>>
 >>> One Blocker(HADOOP-16963) confirmation and following jira's are
 open as
 >>> these needs to merged to other branches(I am tracking the same,
 Ideally
 >>> this can be closed and can raise seperate jira's to track).
 >>>
 >>>
 >>> 1–4 of 4Refresh results
 >>> <
 >>>
 https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
 
 >>> Columns
 >>> Patch InfoKeyTSummaryAssigneeReporterP
 StatusResolutionUpdatedDueCreated
 >>>  HDFS-14353
 >>>  [image:
 Sub-task]
 >>> 
 >>>
 >>> HDFS-8031  Erasure
 >>> Coding:
 >>> metrics xmitsInProgress become to negative.
 >>> 
 >>> maobaolong
 >>> <
 https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maobaolong>
 >>> maobaolong
 >>> <
 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Akira Ajisaka]

Hi Brahma,

Thank you for preparing the release.
Could you cut branch-3.3.0? I would like to backport some fixes for 3.3.1
and not for 3.3.0.

Thanks and regards,
Akira

On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula 
wrote:

> Hi All,
>
> we are down to two blockers issues now (YARN-10194 and YARN-9848) which
> are in patch available state.Hopefully we can out the RC soon.
>
> thanks to @Prabhu Joseph  ,@masakate,@akira
> and @Wei-Chiu Chuang   and others for helping
> resloving the blockers.
>
>
>
> On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula 
> wrote:
>
>>
>> @Prabhu Joseph 
>> >>> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked
>> to branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
>> HADOOP-16982
>> which i will help to review and commit. Thanks.
>>
>> Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
>> blockers. (without YARN-10233 we have given so many releases,it's not newly
>> introduced.).. Thanks
>>
>> @Vinod Kumar Vavilapalli  ,@adam Antal,
>>
>> I noted YARN-9848 as a blocker as you mentioned above.
>>
>> @All,
>>
>> Currently following four blockers are pending for 3.3.0 RC.
>>
>> HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
>>
>>
>>
>> On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
>> vino...@apache.org> wrote:
>>
>>> Looks like a really bad bug to me.
>>>
>>> +1 for revert and +1 for making that a 3.3.0 blocker. I think should
>>> also revert it in a 3.2 maintenance release too.
>>>
>>> Thanks
>>> +Vinod
>>>
>>> > On Apr 14, 2020, at 5:03 PM, Adam Antal 
>>> wrote:
>>> >
>>> > Hi everyone,
>>> >
>>> > Sorry for coming a bit late with this, but there's also one jira that
>>> can
>>> > have potential impact on clusters and we should talk about it.
>>> >
>>> > Steven Rand found this problem earlier and commented to
>>> > https://issues.apache.org/jira/browse/YARN-4946.
>>> > The bug has impact on the RM state store: the RM does not delete apps
>>> - see
>>> > more details in his comment here:
>>> >
>>> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
>>> > .
>>> > (FYI He also created https://issues.apache.org/jira/browse/YARN-9848
>>> with
>>> > the revert task).
>>> >
>>> > It might not be an actual blocker, but since there wasn't any consensus
>>> > about a follow up action, I thought we should decide how to proceed
>>> before
>>> > release 3.3.0.
>>> >
>>> > Regards,
>>> > Adam
>>> >
>>> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
>>> prabhujose.ga...@gmail.com>
>>> > wrote:
>>> >
>>> >> Thanks Brahma for the update.
>>> >>
>>> >> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked
>>> to
>>> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
>>> >> HADOOP-16982
>>> >> which i will help to review and commit. Thanks.
>>> >>
>>> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
>>> >>
>>> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
>>> >> Critical) AND resolution = Unresolved AND "Target Version/s" = 3.3.0
>>> ORDER
>>> >> BY priority DESC
>>> >>
>>> >>
>>> >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
>>> bra...@apache.org>
>>> >> wrote:
>>> >>
>>> >>> *Pending for 3.3.0 Release:*
>>> >>>
>>> >>> One Blocker(HADOOP-16963) confirmation and following jira's are open
>>> as
>>> >>> these needs to merged to other branches(I am tracking the same,
>>> Ideally
>>> >>> this can be closed and can raise seperate jira's to track).
>>> >>>
>>> >>>
>>> >>> 1–4 of 4Refresh results
>>> >>> <
>>> >>>
>>> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
>>> 
>>> >>> Columns
>>> >>> Patch InfoKeyTSummaryAssigneeReporterP
>>> StatusResolutionUpdatedDueCreated
>>> >>>  HDFS-14353
>>> >>>  [image: Sub-task]
>>> >>> 
>>> >>>
>>> >>> HDFS-8031  Erasure
>>> >>> Coding:
>>> >>> metrics xmitsInProgress become to negative.
>>> >>> 
>>> >>> maobaolong
>>> >>> <
>>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maobaolong>
>>> >>> maobaolong
>>> >>> <
>>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maobaolong>
>>> >>> [image:
>>> >>> Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions
>>> >>> <
>>> >>>
>>> https://issues.apache.org/jira/rest/api/1.0/issues/13220750/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
>>> 
>>> >>>  HDFS-14788
>>> >>> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

Hi All,

we are down to two blockers issues now (YARN-10194 and YARN-9848) which are
in patch available state.Hopefully we can out the RC soon.

thanks to @Prabhu Joseph 
,@masakate,@akira and @Wei-Chiu
Chuang   and others for helping resloving the
blockers.



On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula 
wrote:

>
> @Prabhu Joseph 
> >>> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked
> to branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
> HADOOP-16982
> which i will help to review and commit. Thanks.
>
> Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
> blockers. (without YARN-10233 we have given so many releases,it's not newly
> introduced.).. Thanks
>
> @Vinod Kumar Vavilapalli  ,@adam Antal,
>
> I noted YARN-9848 as a blocker as you mentioned above.
>
> @All,
>
> Currently following four blockers are pending for 3.3.0 RC.
>
> HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
>
>
>
> On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> vino...@apache.org> wrote:
>
>> Looks like a really bad bug to me.
>>
>> +1 for revert and +1 for making that a 3.3.0 blocker. I think should also
>> revert it in a 3.2 maintenance release too.
>>
>> Thanks
>> +Vinod
>>
>> > On Apr 14, 2020, at 5:03 PM, Adam Antal 
>> wrote:
>> >
>> > Hi everyone,
>> >
>> > Sorry for coming a bit late with this, but there's also one jira that
>> can
>> > have potential impact on clusters and we should talk about it.
>> >
>> > Steven Rand found this problem earlier and commented to
>> > https://issues.apache.org/jira/browse/YARN-4946.
>> > The bug has impact on the RM state store: the RM does not delete apps -
>> see
>> > more details in his comment here:
>> >
>> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
>> > .
>> > (FYI He also created https://issues.apache.org/jira/browse/YARN-9848
>> with
>> > the revert task).
>> >
>> > It might not be an actual blocker, but since there wasn't any consensus
>> > about a follow up action, I thought we should decide how to proceed
>> before
>> > release 3.3.0.
>> >
>> > Regards,
>> > Adam
>> >
>> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
>> prabhujose.ga...@gmail.com>
>> > wrote:
>> >
>> >> Thanks Brahma for the update.
>> >>
>> >> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked
>> to
>> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
>> >> HADOOP-16982
>> >> which i will help to review and commit. Thanks.
>> >>
>> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
>> >>
>> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
>> >> Critical) AND resolution = Unresolved AND "Target Version/s" = 3.3.0
>> ORDER
>> >> BY priority DESC
>> >>
>> >>
>> >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
>> bra...@apache.org>
>> >> wrote:
>> >>
>> >>> *Pending for 3.3.0 Release:*
>> >>>
>> >>> One Blocker(HADOOP-16963) confirmation and following jira's are open
>> as
>> >>> these needs to merged to other branches(I am tracking the same,
>> Ideally
>> >>> this can be closed and can raise seperate jira's to track).
>> >>>
>> >>>
>> >>> 1–4 of 4Refresh results
>> >>> <
>> >>>
>> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
>> 
>> >>> Columns
>> >>> Patch InfoKeyTSummaryAssigneeReporterP
>> StatusResolutionUpdatedDueCreated
>> >>>  HDFS-14353
>> >>>  [image: Sub-task]
>> >>> 
>> >>>
>> >>> HDFS-8031  Erasure
>> >>> Coding:
>> >>> metrics xmitsInProgress become to negative.
>> >>> 
>> >>> maobaolong
>> >>> <
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maobaolong>
>> >>> maobaolong
>> >>> <
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maobaolong>
>> >>> [image:
>> >>> Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions
>> >>> <
>> >>>
>> https://issues.apache.org/jira/rest/api/1.0/issues/13220750/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
>> 
>> >>>  HDFS-14788
>> >>>  [image:
>> Improvement]
>> >>> 
>> >>>
>> >>> Use dynamic regex filter to ignore copy of source files in Distcp
>> >>> 
>> >>> Mukund Thakur
>> >>> <
>> >>>
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mukund-thakur
>> 
>> >>> Mukund
>> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

@Prabhu Joseph 
>>> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked
to branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
HADOOP-16982
which i will help to review and commit. Thanks.

Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
blockers. (without YARN-10233 we have given so many releases,it's not newly
introduced.).. Thanks

@Vinod Kumar Vavilapalli  ,@adam Antal,

I noted YARN-9848 as a blocker as you mentioned above.

@All,

Currently following four blockers are pending for 3.3.0 RC.

HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.



On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli 
wrote:

> Looks like a really bad bug to me.
>
> +1 for revert and +1 for making that a 3.3.0 blocker. I think should also
> revert it in a 3.2 maintenance release too.
>
> Thanks
> +Vinod
>
> > On Apr 14, 2020, at 5:03 PM, Adam Antal 
> wrote:
> >
> > Hi everyone,
> >
> > Sorry for coming a bit late with this, but there's also one jira that can
> > have potential impact on clusters and we should talk about it.
> >
> > Steven Rand found this problem earlier and commented to
> > https://issues.apache.org/jira/browse/YARN-4946.
> > The bug has impact on the RM state store: the RM does not delete apps -
> see
> > more details in his comment here:
> >
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
> > .
> > (FYI He also created https://issues.apache.org/jira/browse/YARN-9848
> with
> > the revert task).
> >
> > It might not be an actual blocker, but since there wasn't any consensus
> > about a follow up action, I thought we should decide how to proceed
> before
> > release 3.3.0.
> >
> > Regards,
> > Adam
> >
> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
> prabhujose.ga...@gmail.com>
> > wrote:
> >
> >> Thanks Brahma for the update.
> >>
> >> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked to
> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
> >> HADOOP-16982
> >> which i will help to review and commit. Thanks.
> >>
> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
> >>
> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
> >> Critical) AND resolution = Unresolved AND "Target Version/s" = 3.3.0
> ORDER
> >> BY priority DESC
> >>
> >>
> >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
> bra...@apache.org>
> >> wrote:
> >>
> >>> *Pending for 3.3.0 Release:*
> >>>
> >>> One Blocker(HADOOP-16963) confirmation and following jira's are open as
> >>> these needs to merged to other branches(I am tracking the same, Ideally
> >>> this can be closed and can raise seperate jira's to track).
> >>>
> >>>
> >>> 1–4 of 4Refresh results
> >>> <
> >>>
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> 
> >>> Columns
> >>> Patch InfoKeyTSummaryAssigneeReporterP
> StatusResolutionUpdatedDueCreated
> >>>  HDFS-14353
> >>>  [image: Sub-task]
> >>> 
> >>>
> >>> HDFS-8031  Erasure
> >>> Coding:
> >>> metrics xmitsInProgress become to negative.
> >>> 
> >>> maobaolong
> >>> <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maobaolong>
> >>> maobaolong
> >>> <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=maobaolong>
> >>> [image:
> >>> Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions
> >>> <
> >>>
> https://issues.apache.org/jira/rest/api/1.0/issues/13220750/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> 
> >>>  HDFS-14788
> >>>  [image:
> Improvement]
> >>> 
> >>>
> >>> Use dynamic regex filter to ignore copy of source files in Distcp
> >>> 
> >>> Mukund Thakur
> >>> <
> >>>
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mukund-thakur
> 
> >>> Mukund
> >>> Thakur
> >>> <
> >>>
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mukund-thakur
> 
> >>> [image:
> >>> Major] OPEN *Unresolved* 11/Apr/20   28/Aug/19 Actions
> >>> <
> >>>
> https://issues.apache.org/jira/rest/api/1.0/issues/13253437/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> 
> >>>  HDFS-12862
> >>>  [image: Bug]
> >>> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Adam Antal]

Hi everyone,

Sorry for coming a bit late with this, but there's also one jira that can
have potential impact on clusters and we should talk about it.

Steven Rand found this problem earlier and commented to
https://issues.apache.org/jira/browse/YARN-4946.
The bug has impact on the RM state store: the RM does not delete apps - see
more details in his comment here:
https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
.
(FYI He also created https://issues.apache.org/jira/browse/YARN-9848 with
the revert task).

It might not be an actual blocker, but since there wasn't any consensus
about a follow up action, I thought we should decide how to proceed before
release 3.3.0.

Regards,
Adam

On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph 
wrote:

> Thanks Brahma for the update.
>
> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked to
> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
> HADOOP-16982
> which i will help to review and commit. Thanks.
>
> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
>
> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
> Critical) AND resolution = Unresolved AND "Target Version/s" = 3.3.0 ORDER
> BY priority DESC
>
>
> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula 
> wrote:
>
>> *Pending for 3.3.0 Release:*
>>
>> One Blocker(HADOOP-16963) confirmation and following jira's are open as
>> these needs to merged to other branches(I am tracking the same, Ideally
>> this can be closed and can raise seperate jira's to track).
>>
>>
>> 1–4 of 4Refresh results
>> <
>> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
>> >
>> Columns
>> Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
>>  HDFS-14353
>>  [image: Sub-task]
>> 
>>
>> HDFS-8031  Erasure
>> Coding:
>> metrics xmitsInProgress become to negative.
>> 
>> maobaolong
>> 
>> maobaolong
>> 
>> [image:
>> Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions
>> <
>> https://issues.apache.org/jira/rest/api/1.0/issues/13220750/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
>> >
>>  HDFS-14788
>>  [image: Improvement]
>> 
>>
>> Use dynamic regex filter to ignore copy of source files in Distcp
>> 
>> Mukund Thakur
>> <
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mukund-thakur
>> >
>> Mukund
>> Thakur
>> <
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mukund-thakur
>> >
>> [image:
>> Major] OPEN *Unresolved* 11/Apr/20   28/Aug/19 Actions
>> <
>> https://issues.apache.org/jira/rest/api/1.0/issues/13253437/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
>> >
>>  HDFS-12862
>>  [image: Bug]
>> 
>>
>> CacheDirective becomes invalid when NN restart or failover
>> 
>> Wang XL
>> 
>> Wang
>> XL > >
>> [image:
>> Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/17 Actions
>> <
>> https://issues.apache.org/jira/rest/api/1.0/issues/13121225/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
>> >
>>  HDFS-14476
>>  [image: Improvement]
>> 
>>
>> lock too long when fix inconsistent blocks between disk and in-memory
>> 
>> Sean Chow
>> 
>> Sean
>> Chow <
>> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=seanlook>
>> [image:
>> Major] PATCH AVAILABLE *Unresolved* 12/Apr/20   07/May/19 Actions
>> <
>> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Prabhu Joseph]

Thanks Brahma for the update.

Have committed the YARN blocker YARN-10219 to trunk and cherry-picked to
branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
HADOOP-16982
which i will help to review and commit. Thanks.

[image: Screen Shot 2020-04-14 at 1.01.51 PM.png]

project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
Critical) AND resolution = Unresolved AND "Target Version/s" = 3.3.0 ORDER
BY priority DESC


On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula 
wrote:

> *Pending for 3.3.0 Release:*
>
> One Blocker(HADOOP-16963) confirmation and following jira's are open as
> these needs to merged to other branches(I am tracking the same, Ideally
> this can be closed and can raise seperate jira's to track).
>
>
> 1–4 of 4Refresh results
> <
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> >
> Columns
> Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
>  HDFS-14353
>  [image: Sub-task]
> 
>
> HDFS-8031  Erasure
> Coding:
> metrics xmitsInProgress become to negative.
> 
> maobaolong
> 
> maobaolong
> 
> [image:
> Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13220750/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>  HDFS-14788
>  [image: Improvement]
> 
>
> Use dynamic regex filter to ignore copy of source files in Distcp
> 
> Mukund Thakur
>  >
> Mukund
> Thakur
>  >
> [image:
> Major] OPEN *Unresolved* 11/Apr/20   28/Aug/19 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13253437/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>  HDFS-12862
>  [image: Bug]
> 
>
> CacheDirective becomes invalid when NN restart or failover
> 
> Wang XL
> 
> Wang
> XL 
> [image:
> Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/17 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13121225/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>  HDFS-14476
>  [image: Improvement]
> 
>
> lock too long when fix inconsistent blocks between disk and in-memory
> 
> Sean Chow
> 
> Sean
> Chow  >
> [image:
> Major] PATCH AVAILABLE *Unresolved* 12/Apr/20   07/May/19 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13231926/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>
>
> 1–5 of 5Refresh results
> <
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20YARN%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> >
> Columns
> Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
>  YARN-10001
>  [image: Improvement]
> 
>
> Add explanation of unimplemented methods in InMemoryConfigurationStore
> 
> Siddharth Ahuja
> 
> Szilard
> Nemeth <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=snemeth>
> [image:
> Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/19 Actions

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

Thanks Hexiaoqiao for taking care of this jira.Hope other's can do the
needful.

On Sun, Apr 12, 2020 at 11:25 AM Xiaoqiao He  wrote:

> Hi Brahma,
>
> Thanks for your great works here.
> About HDFS-12862 , I try
> to raise another JIRA (HDFS-15272) to track backport branch-3.1, close this
> one to decouple release progress.
>
> Thanks,
> Hexiaoqiao
>
> On Sun, Apr 12, 2020 at 2:49 AM Brahma Reddy Battula 
> wrote:
>
> > *Pending for 3.3.0 Release:*
> >
> > One Blocker(HADOOP-16963) confirmation and following jira's are open as
> > these needs to merged to other branches(I am tracking the same, Ideally
> > this can be closed and can raise seperate jira's to track).
> >
> >
> > 1–4 of 4Refresh results
> > <
> >
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> > >
> > Columns
> > Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
> >  HDFS-14353
> >  [image: Sub-task]
> > 
> >
> > HDFS-8031  Erasure
> > Coding:
> > metrics xmitsInProgress become to negative.
> > 
> > maobaolong
> > 
> > maobaolong
> > 
> > [image:
> > Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions
> > <
> >
> https://issues.apache.org/jira/rest/api/1.0/issues/13220750/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> > >
> >  HDFS-14788
> >  [image: Improvement]
> > 
> >
> > Use dynamic regex filter to ignore copy of source files in Distcp
> > 
> > Mukund Thakur
> > <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mukund-thakur
> > >
> > Mukund
> > Thakur
> > <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mukund-thakur
> > >
> > [image:
> > Major] OPEN *Unresolved* 11/Apr/20   28/Aug/19 Actions
> > <
> >
> https://issues.apache.org/jira/rest/api/1.0/issues/13253437/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> > >
> >  HDFS-12862
> >  [image: Bug]
> > 
> >
> > CacheDirective becomes invalid when NN restart or failover
> > 
> > Wang XL
> > 
> > Wang
> > XL <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=Wang%20XL>
> > [image:
> > Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/17 Actions
> > <
> >
> https://issues.apache.org/jira/rest/api/1.0/issues/13121225/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> > >
> >  HDFS-14476
> >  [image: Improvement]
> > 
> >
> > lock too long when fix inconsistent blocks between disk and in-memory
> > 
> > Sean Chow
> > 
> > Sean
> > Chow <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=seanlook
> > >
> > [image:
> > Major] PATCH AVAILABLE *Unresolved* 12/Apr/20   07/May/19 Actions
> > <
> >
> https://issues.apache.org/jira/rest/api/1.0/issues/13231926/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> > >
> >
> >
> > 1–5 of 5Refresh results
> > <
> >
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20YARN%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> > >
> > Columns
> > Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
> >  YARN-10001
> >  [image: Improvement]
> > 
> >
> > Add explanation of unimplemented methods in InMemoryConfigurationStore
> > 
> > Siddharth Ahuja
> > 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Xiaoqiao He]

Hi Brahma,

Thanks for your great works here.
About HDFS-12862 , I try
to raise another JIRA (HDFS-15272) to track backport branch-3.1, close this
one to decouple release progress.

Thanks,
Hexiaoqiao

On Sun, Apr 12, 2020 at 2:49 AM Brahma Reddy Battula 
wrote:

> *Pending for 3.3.0 Release:*
>
> One Blocker(HADOOP-16963) confirmation and following jira's are open as
> these needs to merged to other branches(I am tracking the same, Ideally
> this can be closed and can raise seperate jira's to track).
>
>
> 1–4 of 4Refresh results
> <
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20HDFS%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> >
> Columns
> Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
>  HDFS-14353
>  [image: Sub-task]
> 
>
> HDFS-8031  Erasure
> Coding:
> metrics xmitsInProgress become to negative.
> 
> maobaolong
> 
> maobaolong
> 
> [image:
> Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13220750/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>  HDFS-14788
>  [image: Improvement]
> 
>
> Use dynamic regex filter to ignore copy of source files in Distcp
> 
> Mukund Thakur
>  >
> Mukund
> Thakur
>  >
> [image:
> Major] OPEN *Unresolved* 11/Apr/20   28/Aug/19 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13253437/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>  HDFS-12862
>  [image: Bug]
> 
>
> CacheDirective becomes invalid when NN restart or failover
> 
> Wang XL
> 
> Wang
> XL 
> [image:
> Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/17 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13121225/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>  HDFS-14476
>  [image: Improvement]
> 
>
> lock too long when fix inconsistent blocks between disk and in-memory
> 
> Sean Chow
> 
> Sean
> Chow  >
> [image:
> Major] PATCH AVAILABLE *Unresolved* 12/Apr/20   07/May/19 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13231926/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
>
>
> 1–5 of 5Refresh results
> <
> https://issues.apache.org/jira/issues/?jql=project%20in%20(%22Hadoop%20YARN%22)%20AND%20resolution%20%3D%20Unresolved%20AND%20(cf%5B12310320%5D%20%3D%203.3.0%20OR%20fixVersion%20%3D%203.3.0)%20ORDER%20BY%20priority%20DESC#
> >
> Columns
> Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
>  YARN-10001
>  [image: Improvement]
> 
>
> Add explanation of unimplemented methods in InMemoryConfigurationStore
> 
> Siddharth Ahuja
> 
> Szilard
> Nemeth <
> https://issues.apache.org/jira/secure/ViewProfile.jspa?name=snemeth>
> [image:
> Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/19 Actions
> <
> https://issues.apache.org/jira/rest/api/1.0/issues/13271213/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin
> >
> 

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

*Pending for 3.3.0 Release:*

One Blocker(HADOOP-16963) confirmation and following jira's are open as
these needs to merged to other branches(I am tracking the same, Ideally
this can be closed and can raise seperate jira's to track).


1–4 of 4Refresh results

Columns
Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
 HDFS-14353
 [image: Sub-task]


HDFS-8031  Erasure Coding:
metrics xmitsInProgress become to negative.

maobaolong

maobaolong

[image:
Major] REOPENED *Unresolved* 11/Apr/20   11/Mar/19 Actions

 HDFS-14788
 [image: Improvement]


Use dynamic regex filter to ignore copy of source files in Distcp

Mukund Thakur

Mukund
Thakur

[image:
Major] OPEN *Unresolved* 11/Apr/20   28/Aug/19 Actions

 HDFS-12862
 [image: Bug]


CacheDirective becomes invalid when NN restart or failover

Wang XL
 Wang
XL 
[image:
Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/17 Actions

 HDFS-14476
 [image: Improvement]


lock too long when fix inconsistent blocks between disk and in-memory

Sean Chow
 Sean
Chow 
[image:
Major] PATCH AVAILABLE *Unresolved* 12/Apr/20   07/May/19 Actions



1–5 of 5Refresh results

Columns
Patch InfoKeyTSummaryAssigneeReporterP StatusResolutionUpdatedDueCreated
 YARN-10001
 [image: Improvement]


Add explanation of unimplemented methods in InMemoryConfigurationStore

Siddharth Ahuja
 Szilard
Nemeth 
[image:
Major] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/19 Actions

 YARN-9997
 [image: Improvement]


Code cleanup in ZKConfigurationStore

Andras Gyori
 Szilard
Nemeth 
[image:
Minor] PATCH AVAILABLE *Unresolved* 11/Apr/20   28/Nov/19 Actions

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

thanks a lot Akira and Prabhu for ping.

All the blockers/critical issues are fixed. Recently two are reported again
like HADOOP-16955 and HADOOP-16963 waiting for confirmation.

@prabhu, Those 156 jira's are non-blocker issues which needs to moved to
3.4.0. and filter for blocker/critical is following.

project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker,
Critical) AND resolution = Unresolved AND "Target Version/s" = 3.3.0 ORDER
BY priority DESC


On Thu, Apr 9, 2020 at 12:09 PM Prabhu Joseph 
wrote:

> Hi Brahma,
>
>  Please let me know if i can be of any help in review and commit /
> clear the pending issues in YARN and MapReduce targeted for 3.3.0.
> I see there are 156 YARN + MapReduce Unresolved Jiras which are either with
> target or fix version set to 3.3.0.
>
> project in (YARN, MAPREDUCE) AND resolution = Unresolved AND (cf[12310320]
> = 3.3.0 OR fixVersion = 3.3.0) ORDER BY priority DESC
>
> Thanks,
> Prabhu Joseph
>
> On Tue, Apr 7, 2020 at 1:27 PM Akira Ajisaka  wrote:
>
> > Hi Brahma,
> >
> > How is this issue going?
> > If there are some blockers, I can help you.
> >
> > -Akira
> >
> > On Mon, Mar 30, 2020 at 3:50 AM Brahma Reddy Battula 
> > wrote:
> >
> > > Hi All,
> > >
> > > branch-3.3 created[1] and trunk  set to 3.4.0-SNAPSHOT.
> > >
> > > while committing jira's please set the proper fix version and if there
> is
> > > any blocker/critical please commit to branch-3.3 or let me know.
> > >
> > > Planning start 3.3.0 RC0 voting on April-4th,2020(as per previous
> > > communication in another thread[2]).
> > >
> > >
> > > 1.https://github.com/apache/hadoop/commits/branch-3.3
> > > 2.
> https://lists.apache.org/list.html?common-dev@hadoop.apache.org:2020-3
> > >
> > >
> > >
> > >
> > > --Brahma Reddy Battula
> > >
> >
>


-- 



--Brahma Reddy Battula

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Prabhu Joseph]

Hi Brahma,

 Please let me know if i can be of any help in review and commit /
clear the pending issues in YARN and MapReduce targeted for 3.3.0.
I see there are 156 YARN + MapReduce Unresolved Jiras which are either with
target or fix version set to 3.3.0.

project in (YARN, MAPREDUCE) AND resolution = Unresolved AND (cf[12310320]
= 3.3.0 OR fixVersion = 3.3.0) ORDER BY priority DESC

Thanks,
Prabhu Joseph

On Tue, Apr 7, 2020 at 1:27 PM Akira Ajisaka  wrote:

> Hi Brahma,
>
> How is this issue going?
> If there are some blockers, I can help you.
>
> -Akira
>
> On Mon, Mar 30, 2020 at 3:50 AM Brahma Reddy Battula 
> wrote:
>
> > Hi All,
> >
> > branch-3.3 created[1] and trunk  set to 3.4.0-SNAPSHOT.
> >
> > while committing jira's please set the proper fix version and if there is
> > any blocker/critical please commit to branch-3.3 or let me know.
> >
> > Planning start 3.3.0 RC0 voting on April-4th,2020(as per previous
> > communication in another thread[2]).
> >
> >
> > 1.https://github.com/apache/hadoop/commits/branch-3.3
> > 2.https://lists.apache.org/list.html?common-dev@hadoop.apache.org:2020-3
> >
> >
> >
> >
> > --Brahma Reddy Battula
> >
>

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Akira Ajisaka]

Hi Brahma,

How is this issue going?
If there are some blockers, I can help you.

-Akira

On Mon, Mar 30, 2020 at 3:50 AM Brahma Reddy Battula 
wrote:

> Hi All,
>
> branch-3.3 created[1] and trunk  set to 3.4.0-SNAPSHOT.
>
> while committing jira's please set the proper fix version and if there is
> any blocker/critical please commit to branch-3.3 or let me know.
>
> Planning start 3.3.0 RC0 voting on April-4th,2020(as per previous
> communication in another thread[2]).
>
>
> 1.https://github.com/apache/hadoop/commits/branch-3.3
> 2.https://lists.apache.org/list.html?common-dev@hadoop.apache.org:2020-3
>
>
>
>
> --Brahma Reddy Battula
>

[Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

Hi All,

branch-3.3 created[1] and trunk  set to 3.4.0-SNAPSHOT.

while committing jira's please set the proper fix version and if there is
any blocker/critical please commit to branch-3.3 or let me know.

Planning start 3.3.0 RC0 voting on April-4th,2020(as per previous
communication in another thread[2]).


1.https://github.com/apache/hadoop/commits/branch-3.3
2.https://lists.apache.org/list.html?common-dev@hadoop.apache.org:2020-3




--Brahma Reddy Battula