kezhuw commented on issue #1276: URL: https://github.com/apache/curator/issues/1276#issuecomment-3264318813
> I think curator(actually internal zookeeper client) will not try to connect server after it retry 3 times and connectionTimeout，but actually I see the log file，zk client seems not controlled by curator? `RetryPolicy` has nothing to do with `start`, it applies only to zookeeper data operations, say `getData`, `setData` and so on. You probably should use `Watcher` in zookeeper or `ConnectionStateListener` in curator to receive state change events. > zk client seems not controlled by curator? the zk client always throw some exception, such as connectionLossException... never stop It is zookeeper's internal behavior. See also [ZOOKEEPER-4508](https://issues.apache.org/jira/browse/ZOOKEEPER-4508), [ZOOKEEPER-4921)(https://issues.apache.org/jira/browse/ZOOKEEPER-4921) and [ZOOKEEPER-4923](https://issues.apache.org/jira/browse/ZOOKEEPER-4923) > until I stop my program. Does `client.stop` help ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
