[
https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870946#action_12870946
]
Qian Ye commented on ZOOKEEPER-779:
-----------------------------------
Thx Patrick, i see your point. Here is some explanation. The temporary glitch
at the starting time will not lead to any harmful result in my system. This
kind of glitch will be recorded in the log file, so some monitor process will
notice that. Moreover, the absence of local meta file or out of sync will not
lead to any harmful result either. In a word, my system should be able to keep
running without zookeeper providing the latest meta info.
I would attach my patch soon :-)
> 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.
