[
https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261835#comment-16261835
]
Duo Zhang commented on HBASE-19312:
-----------------------------------
{quote}
How much work would this be Duo Zhang (This would be preferred all-around I'd
say especially after the work you've done cleaning up zk in client...)
{quote}
Not too much especially that we do not need watcher and is read only. The
difficult is that the construction of ZooKeeper is synchronous, and also the
connection state management is a bit complicated.
The curator team has replied in CURATOR-443 and set the fix version to 4.0.1.
Let's wait for a while to see if they can give a solution.
Thanks.
> Find out why sometimes we need to spend more than one second to get the
> cluster id
> ----------------------------------------------------------------------------------
>
> Key: HBASE-19312
> URL: https://issues.apache.org/jira/browse/HBASE-19312
> Project: HBase
> Issue Type: Bug
> Components: asyncclient, Client, Zookeeper
> Reporter: Duo Zhang
> Priority: Blocker
> Fix For: 2.0.0
>
>
> See the discussion in HBASE-19266.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
