This is an automated email from the ASF dual-hosted git repository. randgalt pushed a commit to branch CURATOR-525-fix-lost-state-race in repository https://gitbox.apache.org/repos/asf/curator.git
commit d9077664cdf9c99042ff5ff34a3aa5a665d0d829 Author: randgalt <[email protected]> AuthorDate: Thu Apr 2 08:16:41 2020 -0500 CURATOR-525 - instead of resetting the connection, change the state to RECONNECTED. I'm concerned about LOST/reset loops. This is still a bad hack and needs to be addressed in the future. --- .../java/org/apache/curator/framework/state/ConnectionStateManager.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/curator-framework/src/main/java/org/apache/curator/framework/state/ConnectionStateManager.java b/curator-framework/src/main/java/org/apache/curator/framework/state/ConnectionStateManager.java index 32ddb78..ca631b6 100644 --- a/curator-framework/src/main/java/org/apache/curator/framework/state/ConnectionStateManager.java +++ b/curator-framework/src/main/java/org/apache/curator/framework/state/ConnectionStateManager.java @@ -295,7 +295,7 @@ public class ConnectionStateManager implements Closeable log.warn("ConnectionState is LOST but isConnected() is true. Resetting connection."); try { - client.getZookeeperClient().reset(); + addStateChange(ConnectionState.RECONNECTED); } catch ( Exception e ) {
