[
https://issues.apache.org/jira/browse/ZOOKEEPER-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268922#comment-13268922
]
Michi Mutsuzaki commented on ZOOKEEPER-1310:
--------------------------------------------
Hi Mark,
ZooKeeper C client is supposed handle reconnect. When the client goes into
CONNECTING_STATE, it's supposed to contact the next server in the server list
provided in zookeeper_init(). It's a bug if it keeps hitting a server that's
down. Please open a separate jira.
I'm not sure if this bug is valid. As Marshall pointed out, you can already
tell when you lose a connection by checking for CONNECTING state. We should
definitely document the timeout/disconnect/reconnect behavior in more details
in zookeeper.h.
--Michi
> 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
