[
https://issues.apache.org/jira/browse/ZOOKEEPER-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144597#comment-13144597
]
Patrick Hunt commented on ZOOKEEPER-1290:
-----------------------------------------
bq. You'll be bounded by the session timeout. That's acceptable?
I meant session expiration. If the server doesn't hear from the client within
the session timeout it will expire the session. If your client takes longer
than this to restart it's session would be expired and it wouldn't be able to
reconnect.
http://zookeeper.apache.org/doc/r3.3.3/zookeeperProgrammers.html#ch_zkSessions
> zookeeper_init_with_watches
> ---------------------------
>
> Key: ZOOKEEPER-1290
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1290
> Project: ZooKeeper
> Issue Type: New Feature
> Components: c client
> Reporter: Marc Celani
>
> Our use of zookeeper requires high scalability, and the underlying data set
> is small and changes infrequently. A persisted cache is ideal for solving
> scalability. We want to treat a restart as if it were a prolonged reconnect -
> that is, maintain the last known zxid and watch list. We would like to expose
> a new zookeeper_init_with_watches api that allows the zhandle to be
> initialized with the watch list and last known zxid. The change would reuse
> the current reconnect logic.
--
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
