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 (JIRA)" <ji...@apache.org> on 2018/10/19 05:32:00 UTC
[jira] [Resolved] (HBASE-21145) Backport "HBASE-21126 Add ability
for HBase Canary to ignore a configurable number of ZooKeeper down nodes"
to branch-2.1
[ https://issues.apache.org/jira/browse/HBASE-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-21145.
---------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
This made it into branch-2.1
tree a23f16c774c0b0e14209741cff4d7652628ec310
parent 63ef89bff71aba8340502ec8b1cbf3fa2a7c550e
author David Manning <da...@salesforce.com> Wed Aug 29 12:06:59 2018 -0700
committer Duo Zhang <zh...@apache.org> Wed Sep 12 10:01:28 2018 +0800
Backport "HBASE-21126 Add ability for HBase Canary to ignore a configurable number of ZooKeeper down nodes" to branch-2.1
Signed-off-by: Josh Elser <el...@apache.org>
Signed-off-by: Duo Zhang <zh...@apache.org>
Resolving.
> Backport "HBASE-21126 Add ability for HBase Canary to ignore a configurable number of ZooKeeper down nodes" to branch-2.1
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-21145
> URL: https://issues.apache.org/jira/browse/HBASE-21145
> Project: HBase
> Issue Type: Improvement
> Components: canary, Zookeeper
> Affects Versions: 1.0.0, 3.0.0, 2.0.0
> Reporter: David Manning
> Assignee: Duo Zhang
> Priority: Minor
> Fix For: 2.1.1
>
> Attachments: HBASE-21126.branch-1.001.patch, HBASE-21126.master.001.patch, HBASE-21126.master.002.patch, HBASE-21126.master.003.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 <N>{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)