You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Stack <st...@duboce.net> on 2018/12/06 04:03:48 UTC
Rolling 2.1.2 and 2.0.4
2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See HBASE-21551
Memory leak when use scan with STREAM at server side.
S
Re: Rolling 2.1.2 and 2.0.4
Posted by Nick Dimiduk <nd...@gmail.com>.
For security-related deprecations, we'll publish a new release of the same
version, with an additional version number appended. For instance, a
critical bug in x.y.z would cause its deprecation, and a new x.y.z.1 be
released in its place, containing as a delta only the patch necessary to
resolve the critical issue.
-n
On Wed, Dec 5, 2018 at 9:56 PM Zach York <zy...@gmail.com>
wrote:
> Do we have a process for deprecating releases with critical bugs? I'm not
> sure this particular bug would warrant that, but I'm just curious if such a
> process is in place.
>
> On Wed, Dec 5, 2018, 9:46 PM Stack <stack@duboce.net wrote:
>
> > Let me put notice on download page too (Let me write the user-list).
> >
> > Wondering if anyone has a bit of time to take a look at the flakeys? For
> > 2.1, they cause a fail every other time:
> >
> >
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.0/lastSuccessfulBuild/artifact/dashboard.html
> >
> > Otherwise I'll try and take a look.
> >
> > Thanks,
> > St.Ack
> >
> > On Wed, Dec 5, 2018 at 9:34 PM Allan Yang <al...@apache.org> wrote:
> >
> > > According to @Zheng Hu, this memory leak was introduced by HBASE-20704
> > > <https://issues.apache.org/jira/browse/HBASE-20704>, which will only
> > > affect
> > > the recently released version 2.0.3 and 2.1.1. I also think we need to
> > > notice those users.
> > > Best Regards
> > > Allan Yang
> > >
> > >
> > > Yu Li <ca...@gmail.com> 于2018年12月6日周四 下午12:46写道：
> > >
> > > > Memory leak is critical enough to roll a new release, and maybe we
> > should
> > > > add a notice somewhere for 2.x users, like our ref guide and/or user
> > > > mailing list? Thanks.
> > > >
> > > > Best Regards,
> > > > Yu
> > > >
> > > >
> > > > On Thu, 6 Dec 2018 at 12:39, Reid Chan <re...@outlook.com>
> wrote:
> > > >
> > > > > +1 for rolling.
> > > > >
> > > > > Nice found, Zheng Hu. (y)
> > > > >
> > > > >
> > > > > --------------------------
> > > > >
> > > > > Best regards,
> > > > > R.C
> > > > >
> > > > >
> > > > >
> > > > > ________________________________________
> > > > > From: Stack <st...@duboce.net>
> > > > > Sent: 06 December 2018 12:03
> > > > > To: HBase Dev List
> > > > > Subject: Rolling 2.1.2 and 2.0.4
> > > > >
> > > > > 2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See
> > HBASE-21551
> > > > > Memory leak when use scan with STREAM at server side.
> > > > >
> > > > > S
> > > > >
> > > >
> > >
> >
>
Re: Rolling 2.1.2 and 2.0.4
Posted by OpenInx <op...@gmail.com>.
> Wondering if anyone has a bit of time to take a look at the flakeys?
For2.1, they cause a fail every other time...
Let me take a look.
On Thu, Dec 6, 2018 at 1:56 PM Zach York <zy...@gmail.com>
wrote:
> Do we have a process for deprecating releases with critical bugs? I'm not
> sure this particular bug would warrant that, but I'm just curious if such a
> process is in place.
>
> On Wed, Dec 5, 2018, 9:46 PM Stack <stack@duboce.net wrote:
>
> > Let me put notice on download page too (Let me write the user-list).
> >
> > Wondering if anyone has a bit of time to take a look at the flakeys? For
> > 2.1, they cause a fail every other time:
> >
> >
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.0/lastSuccessfulBuild/artifact/dashboard.html
> >
> > Otherwise I'll try and take a look.
> >
> > Thanks,
> > St.Ack
> >
> > On Wed, Dec 5, 2018 at 9:34 PM Allan Yang <al...@apache.org> wrote:
> >
> > > According to @Zheng Hu, this memory leak was introduced by HBASE-20704
> > > <https://issues.apache.org/jira/browse/HBASE-20704>, which will only
> > > affect
> > > the recently released version 2.0.3 and 2.1.1. I also think we need to
> > > notice those users.
> > > Best Regards
> > > Allan Yang
> > >
> > >
> > > Yu Li <ca...@gmail.com> 于2018年12月6日周四 下午12:46写道：
> > >
> > > > Memory leak is critical enough to roll a new release, and maybe we
> > should
> > > > add a notice somewhere for 2.x users, like our ref guide and/or user
> > > > mailing list? Thanks.
> > > >
> > > > Best Regards,
> > > > Yu
> > > >
> > > >
> > > > On Thu, 6 Dec 2018 at 12:39, Reid Chan <re...@outlook.com>
> wrote:
> > > >
> > > > > +1 for rolling.
> > > > >
> > > > > Nice found, Zheng Hu. (y)
> > > > >
> > > > >
> > > > > --------------------------
> > > > >
> > > > > Best regards,
> > > > > R.C
> > > > >
> > > > >
> > > > >
> > > > > ________________________________________
> > > > > From: Stack <st...@duboce.net>
> > > > > Sent: 06 December 2018 12:03
> > > > > To: HBase Dev List
> > > > > Subject: Rolling 2.1.2 and 2.0.4
> > > > >
> > > > > 2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See
> > HBASE-21551
> > > > > Memory leak when use scan with STREAM at server side.
> > > > >
> > > > > S
> > > > >
> > > >
> > >
> >
>
Re: Rolling 2.1.2 and 2.0.4
Posted by Zach York <zy...@gmail.com>.
Do we have a process for deprecating releases with critical bugs? I'm not
sure this particular bug would warrant that, but I'm just curious if such a
process is in place.
On Wed, Dec 5, 2018, 9:46 PM Stack <stack@duboce.net wrote:
> Let me put notice on download page too (Let me write the user-list).
>
> Wondering if anyone has a bit of time to take a look at the flakeys? For
> 2.1, they cause a fail every other time:
>
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.0/lastSuccessfulBuild/artifact/dashboard.html
>
> Otherwise I'll try and take a look.
>
> Thanks,
> St.Ack
>
> On Wed, Dec 5, 2018 at 9:34 PM Allan Yang <al...@apache.org> wrote:
>
> > According to @Zheng Hu, this memory leak was introduced by HBASE-20704
> > <https://issues.apache.org/jira/browse/HBASE-20704>, which will only
> > affect
> > the recently released version 2.0.3 and 2.1.1. I also think we need to
> > notice those users.
> > Best Regards
> > Allan Yang
> >
> >
> > Yu Li <ca...@gmail.com> 于2018年12月6日周四 下午12:46写道：
> >
> > > Memory leak is critical enough to roll a new release, and maybe we
> should
> > > add a notice somewhere for 2.x users, like our ref guide and/or user
> > > mailing list? Thanks.
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Thu, 6 Dec 2018 at 12:39, Reid Chan <re...@outlook.com> wrote:
> > >
> > > > +1 for rolling.
> > > >
> > > > Nice found, Zheng Hu. (y)
> > > >
> > > >
> > > > --------------------------
> > > >
> > > > Best regards,
> > > > R.C
> > > >
> > > >
> > > >
> > > > ________________________________________
> > > > From: Stack <st...@duboce.net>
> > > > Sent: 06 December 2018 12:03
> > > > To: HBase Dev List
> > > > Subject: Rolling 2.1.2 and 2.0.4
> > > >
> > > > 2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See
> HBASE-21551
> > > > Memory leak when use scan with STREAM at server side.
> > > >
> > > > S
> > > >
> > >
> >
>
Re: Rolling 2.1.2 and 2.0.4
Posted by Stack <st...@duboce.net>.
Let me put notice on download page too (Let me write the user-list).
Wondering if anyone has a bit of time to take a look at the flakeys? For
2.1, they cause a fail every other time:
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.0/lastSuccessfulBuild/artifact/dashboard.html
Otherwise I'll try and take a look.
Thanks,
St.Ack
On Wed, Dec 5, 2018 at 9:34 PM Allan Yang <al...@apache.org> wrote:
> According to @Zheng Hu, this memory leak was introduced by HBASE-20704
> <https://issues.apache.org/jira/browse/HBASE-20704>, which will only
> affect
> the recently released version 2.0.3 and 2.1.1. I also think we need to
> notice those users.
> Best Regards
> Allan Yang
>
>
> Yu Li <ca...@gmail.com> 于2018年12月6日周四 下午12:46写道：
>
> > Memory leak is critical enough to roll a new release, and maybe we should
> > add a notice somewhere for 2.x users, like our ref guide and/or user
> > mailing list? Thanks.
> >
> > Best Regards,
> > Yu
> >
> >
> > On Thu, 6 Dec 2018 at 12:39, Reid Chan <re...@outlook.com> wrote:
> >
> > > +1 for rolling.
> > >
> > > Nice found, Zheng Hu. (y)
> > >
> > >
> > > --------------------------
> > >
> > > Best regards,
> > > R.C
> > >
> > >
> > >
> > > ________________________________________
> > > From: Stack <st...@duboce.net>
> > > Sent: 06 December 2018 12:03
> > > To: HBase Dev List
> > > Subject: Rolling 2.1.2 and 2.0.4
> > >
> > > 2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See HBASE-21551
> > > Memory leak when use scan with STREAM at server side.
> > >
> > > S
> > >
> >
>
Re: Rolling 2.1.2 and 2.0.4
Posted by Allan Yang <al...@apache.org>.
According to @Zheng Hu, this memory leak was introduced by HBASE-20704
<https://issues.apache.org/jira/browse/HBASE-20704>, which will only affect
the recently released version 2.0.3 and 2.1.1. I also think we need to
notice those users.
Best Regards
Allan Yang
Yu Li <ca...@gmail.com> 于2018年12月6日周四 下午12:46写道：
> Memory leak is critical enough to roll a new release, and maybe we should
> add a notice somewhere for 2.x users, like our ref guide and/or user
> mailing list? Thanks.
>
> Best Regards,
> Yu
>
>
> On Thu, 6 Dec 2018 at 12:39, Reid Chan <re...@outlook.com> wrote:
>
> > +1 for rolling.
> >
> > Nice found, Zheng Hu. (y)
> >
> >
> > --------------------------
> >
> > Best regards,
> > R.C
> >
> >
> >
> > ________________________________________
> > From: Stack <st...@duboce.net>
> > Sent: 06 December 2018 12:03
> > To: HBase Dev List
> > Subject: Rolling 2.1.2 and 2.0.4
> >
> > 2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See HBASE-21551
> > Memory leak when use scan with STREAM at server side.
> >
> > S
> >
>
Re: Rolling 2.1.2 and 2.0.4
Posted by Yu Li <ca...@gmail.com>.
Memory leak is critical enough to roll a new release, and maybe we should
add a notice somewhere for 2.x users, like our ref guide and/or user
mailing list? Thanks.
Best Regards,
Yu
On Thu, 6 Dec 2018 at 12:39, Reid Chan <re...@outlook.com> wrote:
> +1 for rolling.
>
> Nice found, Zheng Hu. (y)
>
>
> --------------------------
>
> Best regards,
> R.C
>
>
>
> ________________________________________
> From: Stack <st...@duboce.net>
> Sent: 06 December 2018 12:03
> To: HBase Dev List
> Subject: Rolling 2.1.2 and 2.0.4
>
> 2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See HBASE-21551
> Memory leak when use scan with STREAM at server side.
>
> S
>
Re: Rolling 2.1.2 and 2.0.4
Posted by Reid Chan <re...@outlook.com>.
+1 for rolling.
Nice found, Zheng Hu. (y)
--------------------------
Best regards,
R.C
________________________________________
From: Stack <st...@duboce.net>
Sent: 06 December 2018 12:03
To: HBase Dev List
Subject: Rolling 2.1.2 and 2.0.4
2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See HBASE-21551
Memory leak when use scan with STREAM at server side.
S
Re: Rolling 2.1.2 and 2.0.4
Posted by Stack <st...@duboce.net>.
To close out this thread, 2.1.2 and 2.0.4 have been released to replace
2.1.1 and 2.0.3. Thew new releases include fixes for the damaging
HBASE-21551.
Thanks,
S
On Wed, Dec 5, 2018 at 8:03 PM Stack <st...@duboce.net> wrote:
> 2.1.1 and 2.0.3 have an ugly bug found by our Zheng Hu. See HBASE-21551
> Memory leak when use scan with STREAM at server side.
>
> S
>