curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Jaton (JIRA)" <>
Subject [jira] [Created] (CURATOR-184) Background retry doesn't stop with LOST event
Date Sun, 18 Jan 2015 20:13:34 GMT
Benjamin Jaton created CURATOR-184:

             Summary: Background retry doesn't stop with LOST event
                 Key: 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

View raw message