[jira] [Resolved] (HBASE-21146) (2.0) Add ability for HBase Canary to ignore a configurable number of ZooKeeper down nodes

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-21146.
---
Resolution: Fixed

Pushed to branch-2.0.

> (2.0) Add ability for HBase Canary to ignore a configurable number of 
> ZooKeeper down nodes
> --
>
> Key: HBASE-21146
> URL: https://issues.apache.org/jira/browse/HBASE-21146
> Project: HBase
>  Issue Type: Improvement
>  Components: canary, Zookeeper
>Affects Versions: 1.0.0, 3.0.0, 2.0.0
>Reporter: David Manning
>Assignee: David Manning
>Priority: Minor
> Fix For: 2.0.4
>
> Attachments: HBASE-21126.branch-1.001.patch, 
> HBASE-21126.master.001.patch, HBASE-21126.master.002.patch, 
> HBASE-21126.master.003.patch, HBASE-21146.branch-2.0.001.patch, 
> zookeeperCanaryLocalTestValidation.txt
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> When running org.apache.hadoop.hbase.tool.Canary with args -zookeeper 
> -treatFailureAsError, the Canary will try to get a znode from each ZooKeeper 
> server in the ensemble. If any server is unavailable or unresponsive, the 
> canary will exit with a failure code.
> If we use the Canary to gauge server health, and alert accordingly, this can 
> be too strict. For example, in a 5-node ZooKeeper cluster, having one node 
> down is safe and expected in rolling upgrades/patches.
> This is a request to allow the Canary to take another parameter
> {code:java}
> -permittedZookeeperFailures {code}
> If N=1, in the 5-node ZooKeeper ensemble example, then the Canary will still 
> pass if 4 ZooKeeper nodes are reachable, but fail if 3 or fewer are reachable.
> (This is my first Jira posting... sorry if I messed anything up.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Rolling 2.1.2 and 2.0.4

[OpenInx]

> 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 
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 
> > 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  wrote:
> >
> > > According to @Zheng Hu, this memory leak was introduced by 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  于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 
> wrote:
> > > >
> > > > > +1 for rolling.
> > > > >
> > > > > Nice found, Zheng Hu. (y)
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Best regards,
> > > > > R.C
> > > > >
> > > > >
> > > > >
> > > > > 
> > > > > From: Stack 
> > > > > 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

[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.

On Wed, Dec 5, 2018, 9:46 PM 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
> 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  wrote:
>
> > According to @Zheng Hu, this memory leak was introduced by 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  于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  wrote:
> > >
> > > > +1 for rolling.
> > > >
> > > > Nice found, Zheng Hu. (y)
> > > >
> > > >
> > > > --
> > > >
> > > > Best regards,
> > > > R.C
> > > >
> > > >
> > > >
> > > > 
> > > > From: Stack 
> > > > 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

[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
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  wrote:

> According to @Zheng Hu, this memory leak was introduced by 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  于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  wrote:
> >
> > > +1 for rolling.
> > >
> > > Nice found, Zheng Hu. (y)
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > R.C
> > >
> > >
> > >
> > > 
> > > From: Stack 
> > > 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
> > >
> >
>

Volunteer needed; test new caching algorithm HBASE-15560

[Stack]

Anyone game to try patch on, HBASE-15560 TinyLFU-based BlockCache, to see
if it caches better in a real-world workload?

Ideal candidate would be interested in better perf and are already keeping
an eye on hit rates. All that is required is testimony as to whether the
patch improves cache hit rates?

Thanks,
S

Re: Rolling 2.1.2 and 2.0.4

[Allan Yang]

According to @Zheng Hu, this memory leak was introduced by 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  于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  wrote:
>
> > +1 for rolling.
> >
> > Nice found, Zheng Hu. (y)
> >
> >
> > --
> >
> > Best regards,
> > R.C
> >
> >
> >
> > 
> > From: Stack 
> > 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
> >
>

[jira] [Resolved] (HBASE-21557) Set version to 2.0.4 on branch-2.0 so can cut an RC

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-21557.
---
   Resolution: Fixed
Fix Version/s: 2.0.4
 Release Note: Set project version to 2.0.4 from 2.0.4-SNAPSHOT

Pushed to branch-2.0.

> Set version to 2.0.4 on branch-2.0 so can cut an RC
> ---
>
> Key: HBASE-21557
> URL: https://issues.apache.org/jira/browse/HBASE-21557
> Project: HBase
>  Issue Type: Sub-task
>  Components: release
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.4
>
>
> $ mvn clean org.codehaus.mojo:versions-maven-plugin:2.5:set -DnewVersion=2.0.4
> $ find . -name pom.xml -exec git add {} \;
> $ git commit ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21557) Set version to 2.0.4 on branch-2.0 so can cut an RC

[stack (JIRA)]

stack created HBASE-21557:
-

 Summary: Set version to 2.0.4 on branch-2.0 so can cut an RC
 Key: HBASE-21557
 URL: https://issues.apache.org/jira/browse/HBASE-21557
 Project: HBase
  Issue Type: Sub-task
  Components: release
Reporter: stack
Assignee: stack


$ mvn clean org.codehaus.mojo:versions-maven-plugin:2.5:set -DnewVersion=2.0.4
$ find . -name pom.xml -exec git add {} \;
$ git commit ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-21558) Set version to 2.1.2 on branch-2.1 so can cut an RC

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-21558.
---
  Resolution: Fixed
Release Note: Set version to 2.1.2 from 2.1.2-SNAPSHOT

Pushed to branch-2.1

> Set version to 2.1.2 on branch-2.1 so can cut an RC
> ---
>
> Key: HBASE-21558
> URL: https://issues.apache.org/jira/browse/HBASE-21558
> Project: HBase
>  Issue Type: Sub-task
>  Components: release
>Reporter: stack
>Assignee: stack
>Priority: Major
>
> mvn clean org.codehaus.mojo:versions-maven-plugin:2.5:set -DnewVersion=2.1.2
> $ find . -name pom.xml -exec git add {} \;
> $ git commit ...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21558) Set version to 2.1.2 on branch-2.1 so can cut an RC

[stack (JIRA)]

stack created HBASE-21558:
-

 Summary: Set version to 2.1.2 on branch-2.1 so can cut an RC
 Key: HBASE-21558
 URL: https://issues.apache.org/jira/browse/HBASE-21558
 Project: HBase
  Issue Type: Sub-task
  Components: release
Reporter: stack
Assignee: stack






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Rolling 2.1.2 and 2.0.4

[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


On Thu, 6 Dec 2018 at 12:39, Reid Chan  wrote:

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

[jira] [Created] (HBASE-21556) Create 2.1.2 release

[stack (JIRA)]

stack created HBASE-21556:
-

 Summary: Create 2.1.2 release
 Key: HBASE-21556
 URL: https://issues.apache.org/jira/browse/HBASE-21556
 Project: HBase
  Issue Type: Task
Reporter: stack
Assignee: stack






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Rolling 2.1.2 and 2.0.4

[Reid Chan]

+1 for rolling.

Nice found, Zheng Hu. (y)


--

Best regards,
R.C




From: Stack 
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

[jira] [Created] (HBASE-21555) Create 2.0.4 release

[stack (JIRA)]

stack created HBASE-21555:
-

 Summary: Create 2.0.4 release
 Key: HBASE-21555
 URL: https://issues.apache.org/jira/browse/HBASE-21555
 Project: HBase
  Issue Type: Task
Reporter: stack
Assignee: stack






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Rolling 2.1.2 and 2.0.4

[Stack]

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

[jira] [Created] (HBASE-21554) Show replication endpoint classname for replication peer on master web UI

[Guanghao Zhang (JIRA)]

Guanghao Zhang created HBASE-21554:
--

 Summary: Show replication endpoint classname for replication peer 
on master web UI
 Key: HBASE-21554
 URL: https://issues.apache.org/jira/browse/HBASE-21554
 Project: HBase
  Issue Type: Improvement
Reporter: Guanghao Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21553) schedLock not released ni MasterProcedureScheduler

[Xu Cang (JIRA)]

Xu Cang created HBASE-21553:
---

 Summary: schedLock not released ni MasterProcedureScheduler
 Key: HBASE-21553
 URL: https://issues.apache.org/jira/browse/HBASE-21553
 Project: HBase
  Issue Type: Improvement
Reporter: Xu Cang


https://github.com/apache/hbase/blob/branch-1/hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/MasterProcedureScheduler.java#L749



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: About to release 1.4.9

[Andrew Purtell]

Looking good. I pushed up 1.4.9RC1 tags and artifacts. Currently cluster
testing with the usual tools. When done I'll call the vote. Should be soon.

On Tue, Dec 4, 2018 at 8:43 AM Andrew Purtell  wrote:

> Needed another round with HBASE-21464. I plan to commit a fix for this
> today, to unblock the release, and roll a new RC.
>
>
> On Thu, Nov 29, 2018 at 5:55 PM Andrew Purtell 
> wrote:
>
>> Now that HBASE-21464 is in it is time for 1.4.9 RC0. Preparing and
>> testing tomorrow. Should have a vote on it next week.
>>
>> --
>> Best regards,
>> Andrew
>>
>> Words like orphans lost among the crosstalk, meaning torn from truth's
>> decrepit hands
>>- A23, Crosstalk
>>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

[jira] [Created] (HBASE-21552) backport HBASE-16735(Procedure v2 - Fix yield while holding locks) to branch-1 .

[Xu Cang (JIRA)]

Xu Cang created HBASE-21552:
---

 Summary: backport  HBASE-16735(Procedure v2 - Fix yield while 
holding locks)  to branch-1 . 
 Key: HBASE-21552
 URL: https://issues.apache.org/jira/browse/HBASE-21552
 Project: HBase
  Issue Type: Improvement
  Components: proc-v2
Reporter: Xu Cang
Assignee: Xu Cang
 Attachments: Screen Shot 2018-12-05 at 4.34.05 PM.png

Please see screenshot for the stack trace. 
We met this issue in production: many createNamespaceProcedures cannot proceed.
After some debugging and JIRA digging, I think HBASE-16735 addressed this 
issue. It fixed the issue that WAITING procedure fails to be added back to the 
runQueue. 
But that change wasn't ported to branch-1. I am creating this JIRA for 
backporting it to branch-1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21551) Memory leak when use scan with STREAM at server side

[Zheng Hu (JIRA)]

Zheng Hu created HBASE-21551:


 Summary: Memory leak when use scan with STREAM at server side
 Key: HBASE-21551
 URL: https://issues.apache.org/jira/browse/HBASE-21551
 Project: HBase
  Issue Type: Bug
Reporter: Zheng Hu
Assignee: Zheng Hu
 Fix For: 3.0.0, 2.2.0, 2.1.2, 2.0.4






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21550) Should allow returning a modified TableDescriptor for MasterObserver.preCreateTable

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-21550:
-

 Summary: Should allow returning a modified TableDescriptor for 
MasterObserver.preCreateTable
 Key: HBASE-21550
 URL: https://issues.apache.org/jira/browse/HBASE-21550
 Project: HBase
  Issue Type: Bug
  Components: Coprocessors
Reporter: Duo Zhang
 Fix For: 3.0.0, 2.2.0


Before 2.0, we will pass a HTableDescriptor and the CPs can modify the schema 
of a table, but now we will pass a TableDescriptor, which is immutable. I think 
it is correct to pass an immutable instance here, but we should have a return 
value for this method to allow CPs to return a new TableDescriptor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)