[
https://issues.apache.org/jira/browse/CURATOR-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066691#comment-16066691
]
Enrico Olivelli commented on CURATOR-408:
-----------------------------------------
[~randgalt]
I am starting to implement this patch.
Actually what is the best way to link to current ZK 3.5.4 snapshot version ?
ZooKeeper snapshots are not published
Do I have to import the ZK Jar in my own local maven repo?
In this case no one could test the patch
If you think this is the best approach I will go on
> Handle graceful close of ZookKeeper client waiting for all resources to be
> released
> -----------------------------------------------------------------------------------
>
> Key: CURATOR-408
> URL: https://issues.apache.org/jira/browse/CURATOR-408
> Project: Apache Curator
> Issue Type: Improvement
> Components: Client
> Affects Versions: 3.4.0
> Reporter: Enrico Olivelli
> Assignee: Enrico Olivelli
>
> Ths idea is to leverage the new ZooKeeper#close(timeoutMs) method introduced
> with ZOOKEEPER-2697.
> This new method waits for the internal threads to finish, this way the client
> is sure that all internal resources handled but low-level ZooKeeper client
> have been released.
> This is very useful in tests because the user can wait for the test
> environment to be cleared.
> In some cases you want to return from the 'close' method as soon as
> possibile. In ZooKeeper a new specific method as been added in order to let
> the user ask for a specific behaviour.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
