cammckenzie commented on pull request #376: URL: https://github.com/apache/curator/pull/376#issuecomment-745552963
@jmslocum16 I probably worded my question poorly. The retry policy will certainly execute a retry on connection loss, but if that retry fails after the configured number of attempts, the error will propagate back to the client which must then do something with it. I was thinking that perhaps you were suggesting something like the Curator guaranteed deletes, which will retry indefinitely until the zNode in question no longer exists (this approach of retrying in the background indefinitely obviously won't work for create / update cases). I will try and take a look at your updates today. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
