[
https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-779:
-----------------------------------
Status: Open (was: Patch Available)
No worries. I'm cancelling the patch for now given that we'd like to approach
it a different way. I've started a document for this feature here:
http://wiki.apache.org/hadoop/ZooKeeper/ConnectionStrategy
Feel free to review and provide feedback, or update the page directly, etc...
> 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, 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.
