[
https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870714#action_12870714
]
Patrick Hunt commented on ZOOKEEPER-779:
----------------------------------------
Sure, attach a patch if you'd like someone to review.
What happens if there is a temporary glitch, immediately after you call init
the client can connect to the ensemble, what do you do then? Also, what happens
if the "local file" meta information is out of sync with what's in ZK, it could
be the case that a subset of clients (the ones not connected to the ensemble)
would be operating differently from the connected clients, no?
Btw, I'm asking these questions not to give you a hard time but because I've
seen others try to do this before, and it's tricky to get right. :-)
> C Client should check the connectivity to the hosts in zookeeper_init
> ---------------------------------------------------------------------
>
> Key: ZOOKEEPER-779
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-779
> Project: Zookeeper
> Issue Type: Improvement
> Components: c client
> Affects Versions: 3.3.1
> Reporter: Qian Ye
>
> In some scenario, whether the client can connect to zookeeper servers is used
> as a logic condition. If the client cannot connect to the servers, the
> program should turn to another fork. However, current zookeeper_init could
> not tell whether the client can connect to one server or not. It could make
> some users feel confused. I think we should check the connectivity to the
> host in zookeeper_init, so we can tell whether the hosts are avaiable at that
> time or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
