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 <[email protected] 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 <[email protected]> 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 <[email protected]> 于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 <[email protected]> wrote: > > > > > > > +1 for rolling. > > > > > > > > Nice found, Zheng Hu. (y) > > > > > > > > > > > > -------------------------- > > > > > > > > Best regards, > > > > R.C > > > > > > > > > > > > > > > > ________________________________________ > > > > From: Stack <[email protected]> > > > > 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 > > > > > > > > > >
