[
https://issues.apache.org/jira/browse/HBASE-19312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260385#comment-16260385
]
Duo Zhang commented on HBASE-19312:
-----------------------------------
Filed CURATOR-443 to report the problem. A temporary workaround is to call
blockUntilConnected when constructing ZKAsyncRegistry but this is not a
production level code. I think we can use this workaround to make our UTs run
faster first, and wait for the response in CURATOR-443. If it is not likely to
be resolved before 2.0.0 release then let's drop curator first and implement
our own read only async zookeeper at client side.
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)
