[ https://issues.apache.org/jira/browse/CURATOR-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kezhu Wang closed CURATOR-184. ------------------------------ Resolution: Not A Problem It is by design unless {{CuratorFramework.close}} is called. You can custom {{RetryPolicy}} to stop retry on {{SESSIONEXPIRED}}. > Background retry doesn't stop with LOST event > --------------------------------------------- > > Key: CURATOR-184 > URL: https://issues.apache.org/jira/browse/CURATOR-184 > Project: Apache Curator > Issue Type: Bug > Components: Client > Affects Versions: 2.7.1 > Reporter: Benjamin Jaton > Priority: Critical > Attachments: Test.java, output.log > > > Curator's background retry continues far after the LOST event connection > state: > 34347 [CuratorFramework-0] INFO > org.apache.curator.framework.state.ConnectionStateManager - State change: > LOST > 34348 [CuratorFramework-0] ERROR > org.apache.curator.framework.imps.CuratorFrameworkImpl - Background > operation retry gave up > (...) > 81139 [main] DEBUG org.apache.curator.RetryLoop - Retry policy not allowing > retry > org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode > = ConnectionLoss for /test > The LOST event is received at 34347 but the curator calls are still hanging > until 81139. -- This message was sent by Atlassian Jira (v8.20.10#820010)