There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • GitHub comment 25#75306420
    via GitHub by patricklucas
  • GitHub comment 522#158341002
    via GitHub by gkleiman
    • org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss at org.apache.curator.ConnectionState.checkTimeouts( at org.apache.curator.ConnectionState.getZooKeeper( at org.apache.curator.CuratorZookeeperClient.getZooKeeper( at org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation( at org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop( at org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300( at org.apache.curator.framework.imps.CuratorFrameworkImpl$ at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at

    Users with the same issue

    480 times, last one,
    214 times, last one,
    Nikolay Rybak
    2 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    6 more bugmates