[
https://issues.apache.org/jira/browse/ZOOKEEPER-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268996#comment-13268996
]
Mark Gius commented on ZOOKEEPER-1310:
--------------------------------------
I would be happy to open up another ticket for the issues I've been having if
this bug is invalid or unrelated to them.
The Zookeeper C client does in fact try another server in the list when the
actively connected socket closes. However, the Client gives NO indication to
the caller that ALL of the endpoints provided in zookeeper_init are "not
responding."
If you have a set of zookeeper endpoints that changes on a somewhat frequent
basis it is entirely possible that a very old instance of a client is sitting
out there with a list of servers that only include one valid endpoint. If that
endpoint goes down, the Client correctly generates a CONNECTING event. Having
generated this event, the client tries each server in the list, waits a little
while, and repeats. It does this _without informing the caller_ that this loop
is occurring. As a caller, I cannot make an informed decision about what is
actually going on right now.
> C Api should use state CONNECTION_LOSS
> --------------------------------------
>
> Key: ZOOKEEPER-1310
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1310
> Project: ZooKeeper
> Issue Type: New Feature
> Components: c client
> Environment: Linux
> Reporter: Jakub Lekstan
>
> I would like to ZooKeeper let know my watcher (which I'm giving to
> zookeeeper_init) about CONNECTION_LOSS, right the given watcher doesn't know
> that connection is lost due to what I can't do my stuff.
> What you think? If so I could try to create a patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
