[
https://issues.apache.org/jira/browse/HBASE-16010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328275#comment-15328275
]
Matt Warhaftig commented on HBASE-16010:
----------------------------------------
{quote}
"or was the method supposed to be a List<ServerName>
getDrainingRegionServers()? which is what the
ServerManager.getDrainingServersList()?"
{quote}
Yes, you are on top of things Matteo - the method signature was changed from
that preliminary draft to return a List<ServerName> of the draining region
servers.
As of 6/13 the RPC and API methods are written and closely follow the ruby
script's logic. Am hoping to wrap up the development in the next 48 hours.
> 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)
