You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Qian Ye (JIRA)" <ji...@apache.org> on 2010/05/25 07:10:24 UTC
[jira] Updated: (ZOOKEEPER-779) C Client should check the
connectivity to the hosts in zookeeper_init
[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qian Ye updated ZOOKEEPER-779:
------------------------------
Attachment: ZOOKEEPER-779.patch
> 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
> Attachments: ZOOKEEPER-779.patch
>
>
> 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.