Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9F7B0200B2B for ; Mon, 13 Jun 2016 19:44:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9E506160A1A; Mon, 13 Jun 2016 17:44:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 177E0160A3C for ; Mon, 13 Jun 2016 19:44:21 +0200 (CEST) Received: (qmail 40549 invoked by uid 500); 13 Jun 2016 17:44:21 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 40533 invoked by uid 99); 13 Jun 2016 17:44:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jun 2016 17:44:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EF9E82C1F5C for ; Mon, 13 Jun 2016 17:44:20 +0000 (UTC) Date: Mon, 13 Jun 2016 17:44:20 +0000 (UTC) From: "Jerry He (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-16010) Put draining function through Admin API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Jun 2016 17:44:22 -0000 [ https://issues.apache.org/jira/browse/HBASE-16010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327817#comment-15327817 ] Jerry He commented on HBASE-16010: ---------------------------------- Concur with Matteo. We can probably use similar API names as in the ServerManager. We still need to write to ZK node from master, in case one master fails. Then the direct client ZK call is still possible. > Put draining function through Admin API > --------------------------------------- > > Key: HBASE-16010 > URL: https://issues.apache.org/jira/browse/HBASE-16010 > Project: HBase > Issue Type: Improvement > Reporter: Jerry He > Assignee: Matt Warhaftig > Priority: Minor > > Currently, there is no Amdin API for draining function. Client has to interact directly with Zookeeper draining node to add and remove draining servers. > For example, in draining_servers.rb: > {code} > zkw = org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.new(config, "draining_servers", nil) > parentZnode = zkw.drainingZNode > begin > for server in servers > node = ZKUtil.joinZNode(parentZnode, server) > ZKUtil.createAndFailSilent(zkw, node) > end > ensure > zkw.close() > end > {code} > This is not good in cases like secure clusters with protected Zookeeper nodes. > Let's put draining function through Admin API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)