[
https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871232#action_12871232
]
Patrick Hunt commented on ZOOKEEPER-779:
----------------------------------------
I took a look at the patch, I don't see a big problem with this but I'm a
little concerned about changing the semantics of zookeeper_init. Really I'd
like to see us move to the strategy pattern directly rather than take a smaller
step that ppl come to rely on and then we end up having to support (or break)
going fwd. Qian I'm assuming this is working ok for you, but would you be
interested in fleshing out the design of the strategy pattern and putting
together a patch for that?
> 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.
