You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Benjamin Jaton (JIRA)" <ji...@apache.org> on 2015/01/18 21:13:34 UTC

[jira] [Created] (CURATOR-184) Background retry doesn't stop with LOST event

Benjamin Jaton created CURATOR-184:
--------------------------------------

             Summary: 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


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
(v6.3.4#6332)