[
https://issues.apache.org/jira/browse/ZOOKEEPER-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144605#comment-13144605
]
Marc Celani commented on ZOOKEEPER-1290:
----------------------------------------
Yes this is fine, although I am allowing the client to initialize with watches
even if they do not report a previous session (more like reconnect to a second
server in a list of servers, where you send a set watch request). That's
actually my use case. The implementation will still respect existing session
expiration logic when the client supplies a client id.
> 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
