Discussion:
Rolling 2.1.2 and 2.0.4
Stack
2018-12-06 04:03:48 UTC
Permalink
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
Reid Chan
2018-12-06 04:31:17 UTC
Permalink
+1 for rolling.

Nice found, Zheng Hu. (y)


--------------------------

Best regards,
R.C



________________________________________
From: Stack <***@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
Yu Li
2018-12-06 04:46:33 UTC
Permalink
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
Post by Reid Chan
+1 for rolling.
Nice found, Zheng Hu. (y)
--------------------------
Best regards,
R.C
________________________________________
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
Allan Yang
2018-12-06 05:34:42 UTC
Permalink
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
Post by Yu Li
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
Post by Reid Chan
+1 for rolling.
Nice found, Zheng Hu. (y)
--------------------------
Best regards,
R.C
________________________________________
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
Stack
2018-12-06 05:46:12 UTC
Permalink
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
Post by Allan Yang
<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
Post by Yu Li
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
Post by Reid Chan
+1 for rolling.
Nice found, Zheng Hu. (y)
--------------------------
Best regards,
R.C
________________________________________
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
Zach York
2018-12-06 05:56:19 UTC
Permalink
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.
Post by Stack
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
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
Post by Allan Yang
<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
Post by Yu Li
Memory leak is critical enough to roll a new release, and maybe we
should
Post by Allan Yang
Post by Yu Li
add a notice somewhere for 2.x users, like our ref guide and/or user
mailing list? Thanks.
Best Regards,
Yu
Post by Reid Chan
+1 for rolling.
Nice found, Zheng Hu. (y)
--------------------------
Best regards,
R.C
________________________________________
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
Post by Allan Yang
Post by Yu Li
Post by Reid Chan
Memory leak when use scan with STREAM at server side.
S
OpenInx
2018-12-06 06:14:01 UTC
Permalink
Post by Stack
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.
Post by Stack
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.
Post by Stack
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
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.0/lastSuccessfulBuild/artifact/dashboard.html
Post by Stack
Otherwise I'll try and take a look.
Thanks,
St.Ack
Post by Allan Yang
<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
Post by Yu Li
Memory leak is critical enough to roll a new release, and maybe we
should
Post by Allan Yang
Post by Yu Li
add a notice somewhere for 2.x users, like our ref guide and/or user
mailing list? Thanks.
Best Regards,
Yu
Post by Reid Chan
+1 for rolling.
Nice found, Zheng Hu. (y)
--------------------------
Best regards,
R.C
________________________________________
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
Post by Allan Yang
Post by Yu Li
Post by Reid Chan
Memory leak when use scan with STREAM at server side.
S
Nick Dimiduk
2018-12-06 15:55:09 UTC
Permalink
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
Post by Zach York
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.
Post by Stack
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
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.0/lastSuccessfulBuild/artifact/dashboard.html
Post by Stack
Otherwise I'll try and take a look.
Thanks,
St.Ack
Post by Allan Yang
<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
Post by Yu Li
Memory leak is critical enough to roll a new release, and maybe we
should
Post by Allan Yang
Post by Yu Li
add a notice somewhere for 2.x users, like our ref guide and/or user
mailing list? Thanks.
Best Regards,
Yu
Post by Reid Chan
+1 for rolling.
Nice found, Zheng Hu. (y)
--------------------------
Best regards,
R.C
________________________________________
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
Post by Allan Yang
Post by Yu Li
Post by Reid Chan
Memory leak when use scan with STREAM at server side.
S
Loading...